To create all the `Makefile.in's for a package, run the
automake program in the top level directory, with no arguments.
automake will automatically find each appropriate
`Makefile.am' (by scanning `configure.in'; see section Scanning `configure.in')
and generate the corresponding `Makefile.in'. Note that
automake has a rather simplistic view of what constitutes a
package; it assumes that a package has only one `configure.in', at
the top. If your package has multiple `configure.in's, then you
automake in each directory holding a
You can optionally give
automake an argument; `.am' is
appended to the argument and the result is used as the name of the input
file. This feature is generally only used to automatically rebuild an
out-of-date `Makefile.in'. Note that
automake must always
be run from the topmost directory of a project, even if being used to
regenerate the `Makefile.in' in some subdirectory. This is
automake must scan `configure.in', and
automake uses the knowledge that a `Makefile.in' is
in a subdirectory to change its behavior in some cases.
automake accepts the following options:
AC_CANONICAL_HOST. Automake is distributed with several of these files; this option will cause the missing ones to be automatically added to the package, whenever possible. In general if Automake tells you a file is missing, try using this option. By default Automake tries to make a symbolic link pointing to its own copy of the missing file; this can be changed with
--add-missing, causes installed files to be copied. The default is to make a symbolic link.
--add-missing, causes standard files to be rebuilt even if they already exist in the source tree. This involves removing the file from the source tree before creating the new symlink (or, with
--copy, copying the new file).
--gnits. This is the default strictness.
automakecreates all `Makefile.in's mentioned in `configure.in'. This option causes it to only update those `Makefile.in's which are out of date with respect to one of their dependents.
automaketo become errors. Errors affect the exit status of
automake, while warnings do not. `--Wno-error', the default, causes warnings to be treated as warnings only.