Hello,
On Tue, Nov 30, 2004 at 07:02:22AM -0800, Bruce Korb wrote:
would make sense to add AM_LDADD as a synonym for LDADD purely for
that sounds weird. I have an alternative proposal:
Automake could watch for variables named AM_* and if it doesn't
recognize them, it could issue a warning.
* Alexandre Duret-Lutz wrote on Tue, Nov 30, 2004 at 01:49:07AM CET:
There have been questions and even bug reports about this
lately. So here is an attempt to document the difference
between CFLAGS, AM_CFLAGS, and mumble_CFLAGS, how they are
ordered, and how they should be (or not be) used.
Alexandre Duret-Lutz wrote:
This section attempts to answer all these questions. We will mostly
discuss `CPPFLAGS' in our examples, but actually the answer holds for
all the compile flags used in Automake: `CCASFLAGS', `CFLAGS',
`CPPFLAGS', `CXXFLAGS', `FCFLAGS', `FFLAGS', `GCJFLAGS',
Leonardo Boiko wrote:
Maybe you could add a small clarification: that LDADD and LIBADD are
automake-specific variables. As far as I understand, there is a
mumble_LDADD and a LDADD, but not an AM_LDADD, and plain LDADD is not
from the user. Thus LDADD and LIBADD are entirely different from
There have been questions and even bug reports about this
lately. So here is an attempt to document the difference
between CFLAGS, AM_CFLAGS, and mumble_CFLAGS, how they are
ordered, and how they should be (or not be) used.
Suggestions, clarifications, and corrections most welcome.
26.5 Flag
