2006-12-05 Stepan Kasal * doc/autoconf.texi (Configuration Headers): Remove the example with multiple input files. (autoheader Invocation): Encourage `AH_BOTTOM', discouraging multiple input files. Index: doc/autoconf.texi =================================================================== RCS file: /cvsroot/autoconf/autoconf/doc/autoconf.texi,v retrieving revision 1.1112 diff -u -r1.1112 autoconf.texi --- doc/autoconf.texi 28 Nov 2006 03:29:47 -0000 1.1112 +++ doc/autoconf.texi 5 Dec 2006 19:34:44 -0000 @@ -2934,17 +2934,13 @@ Usually the input file is named @address@hidden; however, you can override the input file name by appending to @var{header} a -colon-separated list of input files. Examples: +colon-separated list of input files. For example, you might need to make +the input file name acceptable to @acronym{DOS} variants: @example AC_CONFIG_HEADERS([config.h:config.hin]) -AC_CONFIG_HEADERS([defines.h:defs.pre:defines.h.in:defs.post]) @end example address@hidden -Doing this allows you to keep your file names acceptable to address@hidden variants, or -to prepend and/or append boilerplate to the file. @end defmac @defmac AH_HEADER @@ -3028,11 +3024,18 @@ @cindex @command{autoheader} The @command{autoheader} program can create a template file of C address@hidden statements for @command{configure} to use. If address@hidden invokes @code{AC_CONFIG_HEADERS(@var{file})}, address@hidden creates @address@hidden; if multiple file -arguments are given, the first one is used. Otherwise, address@hidden creates @file{config.h.in}. address@hidden statements for @command{configure} to use. +It searches for the first invocation of @code{AC_CONFIG_HEADERS} in address@hidden sources to determine the name of the template. +(If the first call of @code{AC_CONFIG_HEADERS} specifies more than one +input file name, @command{autoheader} uses the first one.) + +It is recommended that only one input file is used. If you want to append +a boilerplate code, it is preferable to use address@hidden([[#include ]])}. +File @file{conf_post.h} is not processed during the configuration then, +which make things clearer. Analogically, @code{AH_TOP} can be used to +prepend a boilerplate code. In order to do its job, @command{autoheader} needs you to document all of the symbols that you might use. Typically this is done via an