www.delorie.com/gnu/docs/autoconf/autoconf_31.html   search  
 
Buy the book!


Autoconf

[ < ] [ > ]   [ << ] [ Up ] [ >> ]         [Top] [Contents] [Index] [ ? ]

4.9 Running Arbitrary Configuration Commands

You can execute arbitrary commands before, during, and after `config.status' is run. The three following macros accumulate the commands to run when they are called multiple times. AC_CONFIG_COMMANDS replaces the obsolete macro AC_OUTPUT_COMMANDS; see 15.4 Obsolete Macros, for details.

Macro: AC_CONFIG_COMMANDS (tag..., [cmds], [init-cmds])
Specify additional shell commands to run at the end of `config.status', and shell commands to initialize any variables from configure. Associate the commands with tag. Since typically the cmds create a file, tag should naturally be the name of that file. This macro is one of the instantiating macros; see 4.5 Performing Configuration Actions.

Here is an unrealistic example:
 
fubar=42
AC_CONFIG_COMMANDS([fubar],
                   [echo this is extra $fubar, and so on.],
                   [fubar=$fubar])

Here is a better one:
 
AC_CONFIG_COMMANDS([time-stamp], [date >time-stamp])

Macro: AC_CONFIG_COMMANDS_PRE (cmds)
Execute the cmds right before creating `config.status'.

Macro: AC_CONFIG_COMMANDS_POST (cmds)
Execute the cmds right after creating `config.status'.


  webmaster   donations   bookstore     delorie software   privacy  
  Copyright 2003   by The Free Software Foundation     Updated Jun 2003