Re: Setting libXXX_la_CPPFLAGS and libXXX_la_CFLAGS erases AM_CPPFLAGS and AM_CFLAGS

2022-11-19 Thread madmurphy
erase everything)… --madmurphy On Fri, Nov 18, 2022 at 11:42 PM Jan Engelhardt wrote: > > On Friday 2022-11-18 22:57, Russ Allbery wrote: > >madmurphy writes: > > > >> However, if at the same time I set also the libfoo_la_CPPFLAGS variable > (no > >> m

Setting libXXX_la_CPPFLAGS and libXXX_la_CFLAGS erases AM_CPPFLAGS and AM_CFLAGS

2022-11-18 Thread madmurphy
LAGS\"" ... libfoo_la_CPPFLAGS = \ $(AM_CPPFLAGS) \ "-DLIBFOO_DUMMY=\"This is just a dummy text\"" In this case libfoo_func() will correctly print Message from the build system: correctly defined via AM_CPPFLAGS Is this a wanted behavior? Isn't the sense of AM_* variables that of being applied to every single library in a project? --madmurphy libfoo-1.0.0.tar.xz Description: application/xz