Re: Setting libXXX_la_CPPFLAGS and libXXX_la_CFLAGS erases AM_CPPFLAGS and AM_CFLAGS

[madmurphy]

I guess it does make sense. But then what might be missing to Automake are
libXXX_la_AM_CFLAGS, libXXX_la_AM_CPPFLAGS and libXXX_la_AM_LDFLAGS
variables, in which the global AM_CFLAGS, AM_CPPFLAGS and AM_LDFLAGS are
automatically pasted (whereas the corresponding versions without the AM_
prefix erase everything)…

--madmurphy

On Fri, Nov 18, 2022 at 11:42 PM Jan Engelhardt <jengelh@inai.de> wrote:

>
> On Friday 2022-11-18 22:57, Russ Allbery wrote:
> >madmurphy <madmurphy333@gmail.com> writes:
> >
> >> However, if at the same time I set also the libfoo_la_CPPFLAGS variable
> (no
> >> matter the content), as in the following example,
> >
> >> AM_CPPFLAGS = \
> >>       "-DLIBFOO_BUILD_MESSAGE=\"correctly defined via AM_CPPFLAGS\""
> >> libfoo_la_CPPFLAGS = \
> >>       "-DLIBFOO_DUMMY=\"This is just a dummy text\""
> >
> >> the AM_CPPFLAGS variable will be completely overwritten
>
> It makes sense though.
>
> It's better that pertarget_CPPFLAGS overwrites, because otherwise... there
> would be no chance to dump (get rid) the AM_CPPFLAGS portion in the
> command-line - short of never setting AM_CPPFLAGS at all, which is not very
> economical if all you want to change is one target...
>