Re: AM_CFLAGS usage

[Ralf Corsepius]

On Mon, 2006-06-12 at 10:16 +0200, Norbert Sendetzky wrote:
> Hi Ralf
> 
> > > Norbert Sendetzky wrote:
> > > > This works, but as soon as I move AM_CFLAGS to the Makefile.am in the
> > > > parent directory, they aren't set any more. Is this the way it was
> > > > intended and the only way to set them globally is to AC_SUBST them or
> > > > is there something wrong in my files?
> >
> > Besides the information Marc already gave you, what's wrong with
> > globally setting it by AC_SUBSTing?  You can still override it per
> > Makefile.am.
> >
> > Note though that
> >   -Wall -ansi -pedantic
> >
> > is pretty GCC specific, and will make many other compilers barf
> > heavily.  So if your package targets portability, it'd be nice
> > to allow your users to override these flags (preferably by
> > ./configure CFLAGS='...').
> 
> How can I do this?

NOTE: CFLAGS !!

Not using AM_CFLAGS=-Wall -ansi -pedantic

and 
./configure CFLAGS="-Wall -ansi -pedantic"

is what Ralf W. is referring to.

> According to the docs, AM_CFLAGS will be overwritten by package specific 
> flags 
> but not by flags provided by the user.
Nope. CFLAGS and AM_CFLAGS are being concatenated inside of a Makefile
using AM_CFLAGS.

Ralf