[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
Every time Automake is run it calls Autoconf to trace `configure.in'. This way it can recognize the use of certain macros and tailor the generated `Makefile.in' appropriately. Currently recognized macros and their effects are:
AC_CONFIG_HEADERS
AM_CONFIG_HEADER
(see section 5.6 Autoconf macros supplied with Automake); this is no longer the case today.
AC_CONFIG_AUX_DIR
AC_CANONICAL_HOST
AC_CANONICAL_SYSTEM
AC_CANONICAL_HOST
, but also defines the
`Makefile' variables `build_alias' and `target_alias'.
See section `Getting the Canonical System Type' in The Autoconf Manual.
AC_LIBSOURCE
AC_LIBSOURCES
AC_LIBOBJ
AC_LIBSOURCE
or AC_LIBSOURCES
.
Note that the AC_LIBOBJ
macro calls AC_LIBSOURCE
. So if
an Autoconf macro is documented to call AC_LIBOBJ([file])
, then
`file.c' will be distributed automatically by Automake. This
encompasses many macros like AC_FUNC_ALLOCA
,
AC_FUNC_MEMCMP
, AC_REPLACE_FUNCS
, and others.
By the way, direct assignments to LIBOBJS
are no longer
supported. You should always use AC_LIBOBJ
for this purpose.
See section `AC_LIBOBJ
vs. LIBOBJS
' in The Autoconf Manual.
AC_PROG_RANLIB
AC_PROG_CXX
AC_PROG_F77
AC_F77_LIBRARY_LDFLAGS
AC_PROG_LIBTOOL
libtool
(see section `Introduction' in The Libtool Manual).
AC_PROG_YACC
AC_PROG_LEX
AC_SUBST
If the Autoconf manual says that a macro calls AC_SUBST
for
var, or defined the output variable var then var will
be defined in each generated `Makefile.in'.
E.g. AC_PATH_XTRA
defines X_CFLAGS
and X_LIBS
, so
you can use the variable in any `Makefile.am' if
AC_PATH_XTRA
is called.
AM_C_PROTOTYPES
AM_GNU_GETTEXT
AM_MAINTAINER_MODE
configure
. If this is used, automake
will cause
`maintainer-only' rules to be turned off by default in the
generated `Makefile.in's. This macro defines the
`MAINTAINER_MODE' conditional, which you can use in your own
`Makefile.am'.
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |