AM_INIT_AUTOMAKE([OPTIONS])
Today, AM_INIT_AUTOMAKE
is called with a single argument: a
space-separated list of Automake options that should
be applied to every Makefile.am in the tree. The effect is as if
each option were listed in AUTOMAKE_OPTIONS
(see Options).
This macro can also be called in another, deprecated form (support
for which will be removed in the next major Automake release (1.13)):
AM_INIT_AUTOMAKE(PACKAGE, VERSION, [NO-DEFINE])
. In this form,
there are two required arguments: the package and the version number.
This form is obsolete because the package and version can
be obtained from Autoconf's AC_INIT
macro (which itself has an
old and a new form).
AC_INIT([src/foo.c]) AM_INIT_AUTOMAKE([mumble], [1.5])
you should modernize it as follows:
AC_INIT([mumble], [1.5]) AC_CONFIG_SRCDIR([src/foo.c]) AM_INIT_AUTOMAKE
Note that if you're upgrading your configure.ac from an earlier
version of Automake, it is not always correct to simply move the
package and version arguments from AM_INIT_AUTOMAKE
directly to
AC_INIT
, as in the example above. The first argument to
AC_INIT
should be the name of your package (e.g., ‘GNU
Automake’), not the tarball name (e.g., ‘automake’) that you used
to pass to AM_INIT_AUTOMAKE
. Autoconf tries to derive a
tarball name from the package name, which should work for most but not
all package names. (If it doesn't work for yours, you can use the
four-argument form of AC_INIT
to provide the tarball name
explicitly).
By default this macro AC_DEFINE
's PACKAGE
and
VERSION
. This can be avoided by passing the no-define
option:
AM_INIT_AUTOMAKE([gnits 1.5 no-define dist-bzip2])
AM_PATH_LISPDIR
lispdir
to the full path to Emacs' site-lisp
directory.
Note that this test assumes the emacs found to be a version
that supports Emacs Lisp (such as GNU Emacs or XEmacs). Other
emacsen can cause this test to hang (some, like old versions of
MicroEmacs, start up in interactive mode, requiring C-x C-c to
exit, which is hardly obvious for a non-emacs user). In most cases,
however, you should be able to use C-c to kill the test. In
order to avoid problems, you can set EMACS to “no” in the
environment, or use the --with-lispdir option to
configure to explicitly set the correct path (if you're sure
you have an emacs that supports Emacs Lisp).
AM_PROG_AR(
[act-if-fail])
AM_PROG_AS
CCAS
, and will also set CCASFLAGS
if required.
AM_PROG_CC_C_O
AC_PROG_CC_C_O
, but it generates its results in
the manner required by Automake. You must use this instead of
AC_PROG_CC_C_O
when you need this functionality, that is, when
using per-target flags or subdir-objects with C sources.
AM_PROG_LEX
AC_PROG_LEX
(see Particular Program Checks), but uses the
missing script on systems that do not have lex.
HP-UX 10 is one such system.
AM_PROG_GCJ
GCJ
and GCJFLAGS
. gcj is the Java front-end to the
GNU Compiler Collection.
AM_PROG_UPC([
compiler-search-list])
UPC
variable. The default compiler-search-list is ‘upcc upc’.
This macro will abort configure if no Unified Parallel C
compiler is found.
AM_MISSING_PROG(
name,
program)
AM_SILENT_RULES
AM_WITH_DMALLOC
WITH_DMALLOC
and add -ldmalloc to LIBS
.