On Aug 27, 2007, at 2:51 PM, Thien-Thi Nguyen wrote:
() Benoit SIGOURE <[EMAIL PROTECTED]> () Mon, 27 Aug 2007 09:48:16 +0200 AM_CFLAGS is reserved for developers. It's not a problem if the user overrides the default value of CFLAGS since CFLAGS is reserved for the user. i understand, and am actually trying achieve, this. my point is that it is the auto* tools themselves that are not helping, or at least i don't know how to request their help to arrange for a situation where "AM_CFLAGS is reserved for developers". what i see is that configure sets CFLAGS and *not* AM_CFLAGS, in apparently normal usage. it seems a contradiction between what is espoused in the docs and what actually happens.
OK look, here is how it goes AFAIK: - You want to set project-wide flags, use AM_CFLAGS- Your user wants to set project-wide flags, it does: ./configure CFLAGS=... - If your user didn't set project-wide flags, AM_PROG_CC may put some default flags in CFLAGS (that can be safely overridden by the user)
What's wrong with this? -- Benoit Sigoure aka Tsuna EPITA Research and Development Laboratory
PGP.sig
Description: This is a digitally signed message part