FYI: AC_CONFIG_FILES doco

[Alexandre Duret-Lutz]

I'm installing this on HEAD.

2005-02-07  Alexandre Duret-Lutz  <address@hidden>

        * doc/automake.texi (Requirements): Show one example of
        AC_CONFIG_FILES with multiple outputs, and correct a few typos.

Index: doc/automake.texi
===================================================================
RCS file: /cvs/automake/automake/doc/automake.texi,v
retrieving revision 1.94
diff -u -r1.94 automake.texi
--- doc/automake.texi   6 Feb 2005 12:33:31 -0000       1.94
+++ doc/automake.texi   7 Feb 2005 22:47:26 -0000
@@ -1286,6 +1286,21 @@
 @itemx AC_OUTPUT
 @acindex AC_CONFIG_FILES
 @acindex AC_OUTPUT
+These two macros are usually invoked as follows near the end of
address@hidden
+
address@hidden
address@hidden
+AC_CONFIG_FILES([
+  Makefile
+  doc/Makefile
+  src/Makefile
+  src/lib/Makefile
+  @dots{}
+])
+AC_OUTPUT
address@hidden example
+
 Automake uses these to determine which files to create (@pxref{Output, ,
 Creating Output Files, autoconf, The Autoconf Manual}).  A listed file
 is considered to be an Automake generated @file{Makefile} if there
@@ -1301,14 +1316,14 @@
 
 Files created by @code{AC_CONFIG_FILES}, be they Automake
 @file{Makefile}s or not, are all removed by @code{make distclean}.
-Their inputs are automatically distributed, except for input that
-turns out the be the outputs of prior @code{AC_CONFIG_FILES} commands.
+Their inputs are automatically distributed, except for inputs that
+turn out the be outputs of prior @code{AC_CONFIG_FILES} commands.
 Finally, rebuild rules are generated in the Automake @file{Makefile}
-in the subdirectory of the output file, if there is one, or in the
-top-level @file{Makefile} otherwise.
+existing in the subdirectory of the output file, if there is one, or
+in the top-level @file{Makefile} otherwise.
 
 The above machinery (cleaning, distributing, and rebuilding) works
-fine only if the @code{AC_CONFIG_FILES} specifications contain only
+fine if the @code{AC_CONFIG_FILES} specifications contain only
 literals.  If part of the specification uses shell variables,
 @command{automake} will not be able to fulfil this setup, and you will
 have to complete the missing bits by hand.  For instance on

-- 
Alexandre Duret-Lutz