Node:Configuration Commands, Next:, Previous:Configuration Headers, Up:Setup


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 Obsolete Macros, for details.

AC_CONFIG_COMMANDS (tag..., [cmds], [init-cmds]) Macro
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 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])

AC_CONFIG_COMMANDS_PRE (cmds) Macro
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)])

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