Copyright (C) 2000-2012 |
GNU Info (autoconf.info)Configuration CommandsRunning 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 Note: 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 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 Note: 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'. automatically generated by info2www version 1.2.2.9 |