Gord Matzigkeit <gord@enci.ucalgary.ca>
Greg A. Woods <woods@most.weird.com>
Harlan Stenn <Harlan.Stenn@pfcs.com>
+Harlan Stenn <Harlan.Stenn@pfcs.com>
Henrik Frystyk Nielsen <frystyk@w3.org>
+Jason Molenda <crash@cygnus.co.jp>
Jerome Santini <santini@chambord.univ-orleans.fr>
Jim Meyering <meyering@na-net.ornl.gov>
Joerg-Martin Schwarz <jms@jms.prima.ruhr.de>
Mark Galassi <rosalia@nis.lanl.gov>
Markku Rossi <mtr@ngs.fi>
Noah Friedman <friedman@gnu.ai.mit.edu>
+Nyul Laszlo <nyul@sol.cc.u-szeged.hu>
Thomas Morgan <tmorgan@pobox.com>
Ulrich Drepper <drepper@gnu.ai.mit.edu>
consider having no-gzip option that turns off gzip/GNU tar.
+djm says:
+David> To avoid comments like the one about subdirs getting buried in
+David> the middle of a Makefile.in, how about pushing comments that
+David> start with ### to the top of the Makefile.in (in order)? Sort
+David> of like how Autoconf uses diversions to force initialization
+David> code to the top of configure.
+
+
================================================================
Stuff for aclocal:
Must document aclocal program
+djm says:
+David> A list of autoconf macros that can be required for use with
+David> automake, all in one place, would be helpful.
+
+
================================================================
Libraries:
and is consistent with GNU Automake @value{VERSION}.@*
@sp 2
Published by the Free Software Foundation @*
-675 Massachusetts Avenue, @*
-Cambridge, MA 02139 USA @*
+59 Template Place - Suite 330, @*
+Boston, MA 02111-1307 USA @*
Permission is granted to make and distribute verbatim copies of
this manual provided the copyright notice and this permission notice
@section Strictness
While Automake is intended to be used by maintainers of GNU packages, it
-does make some effort to accomodate those who wish to use it, but do not
-want to use all the GNU conventions.
+does make some effort to accommodate those who wish to use it, but do
+not want to use all the GNU conventions.
To this end, Automake supports three levels of @dfn{strictness} -- the
strictness indicating how stringently Automake should check standards
@cvindex PACKAGE
@cvindex VERSION
@code{PACKAGE} should be the name of the package as it appears when
-bundled for distribution. For instance, Automake definees
-@code{PACKAGE} to be @samp{automake}. @code{VERSION} should be the
-version number of the release that is being developed. We recommend
-that you make @file{configure.in} the only place in your package where
-the version number is defined; this makes releases simpler.
+bundled for distribution. For instance, Automake defines @code{PACKAGE}
+to be @samp{automake}. @code{VERSION} should be the version number of
+the release that is being developed. We recommend that you make
+@file{configure.in} the only place in your package where the version
+number is defined; this makes releases simpler.
Automake requires the use of the macro @code{AC_ARG_PROGRAM} if a
program or script is installed.
@cvindex jm_MAINTAINER_MODE
@end table
-The @samp{fp_} macros are from @value{Francois} Pinard and the
-@samp{jm_} macro is from Jim Meyering. Both sets are included with
-Automake. @code{automake} will tell where the macros can be found if
-they are missing.
+The @samp{fp_} macros are from @value{Francois} Pinard, the @samp{jm_}
+macro is from Jim Meyering, and the @samp{ud_} macro is from Ulrich
+Drepper.. Both sets are included with Automake. @code{automake} will
+tell where the macros can be found if they are missing.
@node Top level
linked to produce @file{hello}.
If @samp{prog_SOURCES} is needed, but not specified, then it defaults to
-the single file @file{prog.c}. Id est in the example above, the
-definition of @code{hello_SOURCES} is actually redundant.
+the single file @file{prog.c}. In the example above, the definition of
+@code{hello_SOURCES} is actually redundant.
@vindex _SOURCES
@vindex SOURCES
@c lex & yacc should have a separate section
Sometimes it is useful to determine the programs that are to be built at
-configure time. For instance, GNU @code{cpio} only builts @code{mt} and
+configure time. For instance, GNU @code{cpio} only builds @code{mt} and
@code{rmt} under special circumstances.
In this case, you must notify @code{Automake} of all the programs that
All header files must be listed somewhere; missing ones will not appear
in the distribution. Often it is most convenient to list uninstalled
headers with the rest of the sources for a program. @xref{A Program}.
+Headers listed in a @samp{_SOURCES} variable need not be listed in any
+@samp{_HEADERS} variable.
Headers can be installed in @code{includedir}, @code{oldincludedir}, or
@code{pkgincludedir}.
All such data files are included in the distribution.
-Here is how @code{autoconf} installs its auxiliary data files:
+Here is how @code{automake} installs its auxiliary data files:
@example
pkgdata_DATA = clean-kr.am clean.am compile-kr.am compile-vars.am \