Re: AC_PROG_CC sets CFLAGS, what about AM_CFLAGS?
() Benoit SIGOURE <[EMAIL PROTECTED]> () Mon, 27 Aug 2007 21:12:28 +0200 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? i don't think anything is "wrong" with how it is SUPPOSED to work (which i understand, but which you do not seem to understand that i understand). don't worry about it. thi
Re: AC_PROG_CC sets CFLAGS, what about AM_CFLAGS?
Beniot wrote: > 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? It gives the user more things to type. H
Re: AC_PROG_CC sets CFLAGS, what about AM_CFLAGS?
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
AC_PROG_CC sets CFLAGS, what about AM_CFLAGS?
() 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. however, i see libtool is not directly culpable, so i cc automake folks, instead, and change the subject line. thi
