From 10faaad494f160b38c4ae05d30ea42435dda3ab4 Mon Sep 17 00:00:00 2001 From: Akim Demaille Date: Tue, 26 Aug 2003 07:36:39 +0000 Subject: [PATCH] * doc/autoconf.texi (Output): Make clear that one can run code after AC_OUTPUT. --- ChangeLog | 5 +++++ doc/autoconf.texi | 10 +++++++++- 2 files changed, 14 insertions(+), 1 deletion(-) diff --git a/ChangeLog b/ChangeLog index 3c605208..6f80eaf5 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,3 +1,8 @@ +2003-08-26 Akim Demaille + + * doc/autoconf.texi (Output): Make clear that one can run code + after AC_OUTPUT. + 2003-08-25 Akim Demaille * config/announce-gen, GNUmakefile, Makefile.maint: Update from diff --git a/doc/autoconf.texi b/doc/autoconf.texi index 28e3f077..a3c97661 100644 --- a/doc/autoconf.texi +++ b/doc/autoconf.texi @@ -1763,7 +1763,7 @@ name is obsolete because some @code{make} have a rule that creates @section Outputting Files Every Autoconf script, e.g., @file{configure.ac}, should finish by -calling @code{AC_OUTPUT}. That is the macro that generates +calling @code{AC_OUTPUT}. That is the macro that generates and runs @file{config.status}, which will create the @file{Makefile}s and any other files resulting from configuration. This is the only required macro besides @code{AC_INIT} (@pxref{Input}). @@ -1782,6 +1782,14 @@ Commands}, macro @code{AC_CONFIG_COMMANDS}), links (see @ref{Configuration Links}, macro @code{AC_CONFIG_LINKS}), subdirectories to configure (see @ref{Subdirectories}, macro @code{AC_CONFIG_SUBDIRS}) are honored. + +The location of your @code{AC_OUTPUT} invocation is the exact point +where configuration actions are taken: any code afterwards will be +executed by @code{configure} once @command{config.status} was run. If +you want to bind actions to @command{config.status} itself +(independently of whether @command{configure} is being run), see +@ref{Configuration Commands, , Running Arbitrary Configuration +Commands}. @end defmac Historically, the usage of @code{AC_OUTPUT} was somewhat different. -- 2.47.2