| Giving a shell variable to AC_CONFIG_LINKS like this doesn't work in
| recent CVS versions of Autoconf:
|
| foo="link:file"
| AC_CONFIG_LINKS($foo)
|
| I assume it's because `config_links' is set in config.status by
| configure doing
|
| cat >$CONFIG_STATUS <<\EOF
| [...]
| config_links="\
| $foo"
| [...]
| EOF
|
| Where the backslash in "\EOF" prevents `foo' from being ``expanded''.
|
| Is this on purpose? If so, any ideas on how to work around it? We
| build a list of "link:file" pairs in quite an elaborate fashion and
| depend on it heavily.
Is it really important for you to be able to use variables? Using
literals is a good thing, since it allows to determine statically the
dependencies created by config.status, so this is a property we would
like to keep.
Nevertheless, there is no intention to complexify your task, so if you
depend crucially upon this, AC_CONFIG_LINK should be changed.
Is it enough to be able to
if ...
AC_CONFIG_LINK(foo:bar)
else
AC_CONFIG_LINK(foo:baz)
fi
?
