* General Operation:: General operation of Automake
* Strictness:: Standards conformance checking
+* Auxiliary files:: Automatic installation of auxiliary files
* Uniform:: The Uniform Naming Scheme
* Length Limitations:: Staying below the command line length limit
* Canonicalization:: How derived variables are named
@menu
* General Operation:: General operation of Automake
* Strictness:: Standards conformance checking
+* Auxiliary files:: Automatic installation of auxiliary files
* Uniform:: The Uniform Naming Scheme
* Length Limitations:: Staying below the command line length limit
* Canonicalization:: How derived variables are named
@xref{Gnits}, for more information on the precise implications of the
strictness level.
+@node Auxiliary files
+@section Automatic installation of auxiliary files
+
+Automake requires certain common files to exist in certain situations;
+for instance, @file{config.guess} is required if @file{configure.ac}
+invokes @code{AC_CANONICAL_HOST}. Automake is distributed with several
+of these files (@pxref{Auxiliary Programs}); @command{automake} will
+automatically add the missing required files to the package, whenever
+needed.
+By default Automake tries to make a symbolic link pointing to its own
+copy of the missing file; this can be changed with @option{--copy}.
+
+Many of the potentially-missing files are common scripts whose
+location may be specified via the @code{AC_CONFIG_AUX_DIR} macro.
+Therefore, @code{AC_CONFIG_AUX_DIR}'s setting affects whether a
+file is considered missing, and where the missing file is added
+(@pxref{Optional}).
+
+In some strictness modes, additional files are installed, see
+@ref{Gnits} for more information.
+
+@cindex auxiliary files, automatic installation
+@cindex Automatic installation of auxiliary files
@node Uniform
@section The Uniform Naming Scheme
info_TEXINFOS = zardoz.texi
@end example
-Now you can run @samp{automake --add-missing} to generate your
-@file{Makefile.in} and grab any auxiliary files you might need, and
-you're done!
+Now you can run @samp{automake} to generate your @file{Makefile.in} and
+grab any auxiliary files you might need, and you're done!
@node true
@cindex @file{config.guess}
@table @code
-@item -a
-@itemx --add-missing
-@opindex -a
-@opindex --add-missing
-Automake requires certain common files to exist in certain situations;
-for instance, @file{config.guess} is required if @file{configure.ac} invokes
-@code{AC_CANONICAL_HOST}. Automake is distributed with several of these
-files (@pxref{Auxiliary Programs}); 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 @option{--copy}.
-
-Many of the potentially-missing files are common scripts whose
-location may be specified via the @code{AC_CONFIG_AUX_DIR} macro.
-Therefore, @code{AC_CONFIG_AUX_DIR}'s setting affects whether a
-file is considered missing, and where the missing file is added
-(@pxref{Optional}).
-
-In some strictness modes, additional files are installed, see @ref{Gnits}
-for more information.
-
@item --libdir=@var{dir}
@opindex --libdir
Look for Automake data files in directory @var{dir} instead of in the
@opindex -c
@itemx --copy
@opindex --copy
-When used with @option{--add-missing}, causes installed files to be
-copied. The default is to make a symbolic link.
+Causes standard files (if any) to be copied. The default is to make a
+symbolic link.
@item -f
@opindex -f
@itemx --force-missing
@opindex --force-missing
-When used with @option{--add-missing}, causes standard files to be reinstalled
-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
-@option{--copy}, copying the new file).
+Causes standard files to be reinstalled 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 @option{--copy}, copying the
+new file).
@item --foreign
@opindex --foreign
special wrapper program called @command{depcomp}. @command{depcomp}
understands how to coax many different C and C++ compilers into
generating dependency information in the format it requires.
-@samp{automake -a} will install @command{depcomp} into your source
+@samp{automake} will install @command{depcomp} into your source
tree for you. If @command{depcomp} can't figure out how to properly
invoke your compiler, dependency tracking will simply be disabled for
your build.
The @file{version.texi} support requires the @command{mdate-sh}
script; this script is supplied with Automake and automatically
-included when @command{automake} is invoked with the
-@option{--add-missing} option.
+included when @command{automake} is invoked.
If you have multiple Texinfo files, and you want to use the
@file{version.texi} feature, then you have to have a separate version
@file{.texi} files. If you used @code{AC_CONFIG_AUX_DIR} in
@file{configure.ac} (@pxref{Input, , Finding `configure' Input,
autoconf, The Autoconf Manual}), then @file{texinfo.tex} is looked for
-there. In both cases, @command{automake} then supplies @file{texinfo.tex} if
-@option{--add-missing} is given, and takes care of its distribution.
+there. In both cases, @command{automake} then supplies @file{texinfo.tex}
+and takes care of its distribution.
However, if you set the @code{TEXINFO_TEX} variable (see below),
it overrides the location of the file and turns off its installation
into the source as well as its distribution.
Autoconf macros such as @code{AC_CONFIG_FILES} and siblings) are
automatically distributed. Files included in a @file{Makefile.am} (using
@code{include}) or in @file{configure.ac} (using @code{m4_include}), and
-helper scripts installed with @samp{automake --add-missing} are also
+helper scripts installed by @samp{automake} itself are also
distributed.
@vindex EXTRA_DIST
and @file{ChangeLog}, plus one of @file{COPYING.LIB}, @file{COPYING.LESSER}
or @file{COPYING}, are required at the topmost directory of the package.
-If the @option{--add-missing} option is given, @command{automake} will
+@command{automake} will by default
add a generic version of the @file{INSTALL} file as well as the
@file{COPYING} file containing the text of the current version of the
GNU General Public License existing at the time of this Automake release
distribute their work under terms like those of the GPL, but doing so
is not required to use Automake.
-Some of the files that can be automatically installed via the
-@option{--add-missing} switch do fall under the GPL@. However, these also
-have a special exception allowing you to distribute them with your
-package, regardless of the licensing you choose.
+Some of the files that can be automatically installed bu @command{automake}
+do fall under the GPL@. However, these also have a special exception
+allowing you to distribute them with your package, regardless of the
+licensing you choose.
@node API Versioning
@item auxiliary tools like @file{install-sh} or @file{py-compile}
@end itemize
-@file{aclocal.m4} is generated by @command{aclocal} and contains some
-Automake-supplied M4 macros. Auxiliary tools are installed by
-@samp{automake --add-missing} when needed. @file{Makefile.in}s are
-built from @file{Makefile.am} by @command{automake}, and rely on the
-definitions of the M4 macros put in @file{aclocal.m4} as well as the
-behavior of the auxiliary tools installed.
+@file{aclocal.m4} is generated by @command{aclocal} and contains
+some Automake-supplied M4 macros. Auxiliary tools are installed
+by @samp{automake} when needed. @file{Makefile.in}s are built
+from @file{Makefile.am} by @command{automake}, and rely on the
+definitions of the M4 macros put in @file{aclocal.m4} as well as
+the behavior of the auxiliary tools installed.
Because all of these files are closely related, it is important to
regenerate all of them when upgrading to a newer Automake release.
@example
aclocal # with any option needed (such a -I m4)
autoconf
-automake --add-missing --force-missing
+automake --force-missing
@end example
@noindent
+++ /dev/null
-#! /bin/sh
-# Copyright (C) 2011-2012 Free Software Foundation, Inc.
-#
-# This program is free software; you can redistribute it and/or modify
-# it under the terms of the GNU General Public License as published by
-# the Free Software Foundation; either version 2, or (at your option)
-# any later version.
-#
-# This program is distributed in the hope that it will be useful,
-# but WITHOUT ANY WARRANTY; without even the implied warranty of
-# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
-# GNU General Public License for more details.
-#
-# You should have received a copy of the GNU General Public License
-# along with this program. If not, see <http://www.gnu.org/licenses/>.
-
-# Automake should stop the creation of Makefile.in files at the first
-# encountered error due to a required auxiliary file not found.
-
-. ./defs || exit 1
-
-cat >> configure.ac <<END
-AM_PATH_PYTHON
-END
-
-echo SUBDIRS = > Makefile.am
-
-for i in 1 2 3 4 5; do
- echo "AC_CONFIG_FILES([sub$i/Makefile])" >> configure.ac
- echo "SUBDIRS += sub$i" >> Makefile.am
- mkdir sub$i
- echo python_PYTHON = foo.py > sub$i/Makefile.am
-done
-
-: > sub1/Makefile.am
-
-$ACLOCAL
-
-unset AUTOMAKE_JOBS || :
-
-AUTOMAKE_fails
-ls -l Makefile.in */Makefile.in || : # For debugging.
-# Top-level Makefile.in might be created or not, we don't want to set
-# too strict semantics here, so don't check for it. But the later
-# files shouldn't exist.
-test -f sub1/Makefile.in
-test ! -e sub2/Makefile.in
-test ! -e sub3/Makefile.in
-test ! -e sub4/Makefile.in
-test ! -e sub5/Makefile.in
-
-rm -f Makefile.in */Makefile.in
-
-: > sub2/Makefile.am
-: > sub3/Makefile.am
-
-AUTOMAKE_fails
-ls -l Makefile.in */Makefile.in || : # For debugging.
-test -f sub1/Makefile.in
-test -f sub2/Makefile.in
-test -f sub3/Makefile.in
-test ! -e sub4/Makefile.in
-test ! -e sub5/Makefile.in
-
-:
projects / thirdparty / automake.git / commitdiff
