Ok, I'm pretty sure that these worked at some point (much like the
prompt-to-add-records code) but it appears that under the current
configure.ac code, specifying --enable-foo=no or --disable-foo
actually switches on feature foo. I can see why this is, but it's a
bit non-intuitive. So, I'm checking in a fix, but if someone more
familiar with autoconf scripts can see a problem with what I've done
(or a cleaner way to fix it) please do contribute.
Cheers,
Waider. and I thought autoconf was supposed to make things *easier*
--
[EMAIL PROTECTED] / Yes, it /is/ very personal of me.
"Multithreadedness, like object-orientedness, is a matter of perception. If it
seems multithreaded, it is. All else is an implementation detail."
- Jamie Zawinski
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
bbdb-info@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bbdb-info
BBDB Home Page: http://bbdb.sourceforge.net/
