Braden McDaniel <braden@xxxxxxxxxxx> writes: > If all your --with argument would be doing is dumbly appending > "/include" and "/lib" for -I and -L flags, I don't see the point. I provide --with-* options for all optional libraries because sometimes they do something else and sometimes they don't, and this way I provide a consistent API to everyone building the package. Actually, I provide three options: --with-foo that sets the prefix, --with-foo-include that sets the -I option only, and --with-foo-lib that sets the -L option only. --with-foo does some work to figure out lib vs. lib32 vs. lib64, and for some libraries it does other things instead. (For Kerberos, for instance, the --with-foo path is used to find the right krb5-config script to run.) -- Russ Allbery (rra@xxxxxxxxxxxx) <http://www.eyrie.org/~eagle/> _______________________________________________ Autoconf mailing list Autoconf@xxxxxxx http://lists.gnu.org/mailman/listinfo/autoconf
