[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: CFLAGS/LDFLAGS vs. --with
From: |
Russ Allbery |
Subject: |
Re: CFLAGS/LDFLAGS vs. --with |
Date: |
Thu, 06 Aug 2009 22:07:16 -0700 |
User-agent: |
Gnus/5.11 (Gnus v5.11) Emacs/22.3 (gnu/linux) |
Braden McDaniel <address@hidden> 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 (address@hidden) <http://www.eyrie.org/~eagle/>