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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ralf Wildenhues wrote:
> One possibility to separate GNU make specific parts and portable make
> parts so that Automake only sees the latter is to put those in
> Makefile.am, put the GNU make specific stuff in GNUmakefile, and let the
> latter 'include
Hello Tom,
* Tom Bachmann wrote on Sat, Jun 24, 2006 at 02:24:09PM CEST:
>
> But automake complains "bad characters in variable name". I could work
> around this by stopping automake from processing the file (make allows
> it), but I could not find a way to do this but $(eval include bar.mk),
> w
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
[please cc me as I'm not registered to the list]
I'm currently digging into how to extend automake. As make can do
(nearly) everything automake can, I suppose I'll end up at a stage where
everyone who wants the new stuff includes a Makefile snippe
