At 6:24 PM -0500 12/3/99, Tom Metro wrote: >If I remember correctly, Ht://Dig's configure doesn't actually ask the >user any questions - it just runs through its automated tests, and the >stuff extracted from an httpd.conf isn't really needed at build time, >so maybe what's needed is a post-build config tool. This could work. >I'm sure this can be accomplished with GNU configure, but I'm not >familiar enough with it to know how. The best solution is to write a small shell script that passes the appropriate options to configure for you. The advantage is that you can have it not only run ./configure --option1... but also make, make check, make install and anything else you might like. Why did we do away with the CONFIG file? It's not as powerful as configure options. In 3.2, for example, you can choose static or shared libraries, enable a "make check" phase and a variety of other options. Plus, many people are familiar with --bindir=, --prefix=, --exec-prefix=, but these didn't quite match the directory choices in the CONFIG file. -Geoff ------------------------------------ To unsubscribe from the htdig3-dev mailing list, send a message to [EMAIL PROTECTED] You will receive a message to confirm this.
