On Saturday 2022-11-19 09:11, madmurphy wrote:
>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 t
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 era
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
>> matter the content), as in the following example,
>
>> AM_CPPFLAGS = \
>> "-DLIBFOO_BUILD_MESSAGE=\"correctly defined via AM_CPPFLAGS\""
>>
madmurphy 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=
Hi,
If I create a library named libfoo containing the following code (example
attached),
#include "libfoo.h"
#ifndef LIBFOO_BUILD_MESSAGE
#define LIBFOO_BUILD_MESSAGE "undefined"
#endif
int libfoo_func() {
printf("Message from the build system: " LIBFOO_BUILD_MESSAGE "\n");
ret
