> On Mon, 2003-08-25 at 08:47, Akim Demaille wrote:
>> > Hi,
>> > Is there any means to run a script at the very end of running
>> > "configure"?
>>
>> > AC_CONFIG_COMMANDS_POST(script) seems to run "script" at the end of
>> > config.status, before recursing into CONFIG_SUBDIRS.
>>
>> > Directly invoking a script from inside of the configure-script invokes
>> > it before config.status has been run, i.e. before config.status has
>> > generated the files it's supposed to be generated.
>>
>> Not if run after AC_OUTPUT.
> Can I consider this behavior to be documented?
How about this?
Index: ChangeLog
from Akim Demaille <akim@xxxxxxxx>
* doc/autoconf.texi (Output): Make clear that one can run code
after AC_OUTPUT.
Index: doc/autoconf.texi
===================================================================
RCS file: /cvsroot/autoconf/autoconf/doc/autoconf.texi,v
retrieving revision 1.754
diff -u -u -r1.754 autoconf.texi
--- doc/autoconf.texi 25 Aug 2003 06:29:48 -0000 1.754
+++ doc/autoconf.texi 26 Aug 2003 07:35:11 -0000
@@ -1763,7 +1763,7 @@
@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 @@
@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.
