Go to the first, previous, next, last section, table of contents.

Running Arbitrary Configuration Commands

You execute arbitrary commands either 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 section Obsolete Macros, for details.

Macro: AC_CONFIG_COMMANDS (tag..., @ovar{cmds}, @ovar{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 to the 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 section Taking 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'. A typical use is computing values derived from variables built during the execution of configure:

AC_CONFIG_COMMANDS_PRE(
[LTLIBOBJS=`echo $LIBOBJS | sed 's/\.o/\.lo/g'`
AC_SUBST(LTLIBOBJS)])

Macro: AC_CONFIG_COMMANDS_POST (cmds)

Execute the cmds right after creating `config.status'.

Go to the first, previous, next, last section, table of contents.