bug-automake
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: .F fix to automake.in


From: Tom Tromey
Subject: Re: .F fix to automake.in
Date: 22 May 2001 11:25:58 -0600

>>>>> "Christian" == Christian Holm Christensen <address@hidden> writes:

>> I don't think we want to do this.  INCLUDES is an old-style variable.
>> Probably we should deprecate it and remove it later.

Christian> What?  How then, is people supposed to specify headers
Christian> paths and defines they may need?

With AM_FFLAGS, or AM_CFLAGS, or AM_CXXFLAGS, or ...

Christian> While you can do a lot with configure macros, there is a
Christian> limit, and suppose you want to #include headers from other
Christian> parts of your source tree, what then?

The capability still exists; only the names have changed.

Christian> By the way, what about per target CPPFLAGS, CFLAGS, and so
Christian> on.

What about them?  As far as I know they work fine with the cvs
automake.

>> You can use `AM_FFLAGS' for what you want.

Christian> Uh.  I thought that variables like AM_... where much more
Christian> 'hands-off' than the those that didn't have that prefix.
Christian> Certainly that's the impression I got from the docs.

The AM_ macros exist for the Makefile.am writer.
The non-AM_ versions exist for the end user (the person building the
package).

Can you suggest a change to the manual to make this more clear?

Tom



reply via email to

[Prev in Thread] Current Thread [Next in Thread]