On 2013-09-11 23:08, Dalibor Topic wrote:
I haven't dug into the code much, but why not use AC_CONFIG_COMMANDS [0] ?
cheers,
dalibor topic
[06
https://www.gnu.org/savannah-checkouts/gnu/autoconf/manual/autoconf-2.69/html_node/Configuration-Commands.html#Configuration-Commands
I haven't actually noticed AC_CONFIG_COMMANDS before; thank you for
pointing it out. Having read the documentation, however, I can't see the
point.
Adding a post-process command using AC_CONFIG_COMMANDS would make it be
the last part of config.status, which is executed as part of AC_OUTPUT.
This is more or less equivalent with executing the code after the
AC_OUTPUT macro call. The only difference, is that it is not stored in
config.status.
The autoconf idea is that you should be able to re-execute config.status
and have your configuration re-created. This is not something we have
ever tested, and I highly doubt it will work, given the complexity of
our configure scripts. Given that, I think wrapping the code in a
AC_CONFIG_COMMANDS will achieve nothing except making the code harder to
understand.
Nevertheless, thanks for the pointer! It might turn out to be useful
some day.
/Magnus
