Re: AM_C*FLAGS and C*FLAGS

2006-06-26 Thread Andre Stechert
The trick is that if we use a configure.ac file to help decide what flags may be needed, >inside< this configure script we need to use CFLAGS and CPPFLAGS to effect the running of configure. Not really. Just AC_SUBST a variable in the AM_CFLAGS or AM_CPPFLAGS directive. E.g., when I write an a

Re: AM_C*FLAGS and C*FLAGS

2006-06-26 Thread Harlan Stenn
> On Mon, 2006-06-26 at 04:34 +, Harlan Stenn wrote: > > We are told that we should not use CPPFLAGS or CFLAGS in a Makefile.am, > > as they are for users. > That's only partially true. > > More precisely: You should not override user-supplied CPPFLAGS, CFLAGS, > CXXFLAGS, LIBS etc. > > Appen

Re: AM_C*FLAGS and C*FLAGS

2006-06-26 Thread Ralf Corsepius
On Mon, 2006-06-26 at 04:34 +, Harlan Stenn wrote: > We are told that we should not use CPPFLAGS or CFLAGS in a Makefile.am, > as they are for users. That's only partially true. More precisely: You should not override user-supplied CPPFLAGS, CFLAGS, CXXFLAGS, LIBS etc. Appending something to

AM_C*FLAGS and C*FLAGS

2006-06-25 Thread Harlan Stenn
We are told that we should not use CPPFLAGS or CFLAGS in a Makefile.am, as they are for users. The trick is that if we use a configure.ac file to help decide what flags may be needed, >inside< this configure script we need to use CFLAGS and CPPFLAGS to effect the running of configure. (I say CFLA