Akim Demaille <[EMAIL PROTECTED]> wrote
25 May 2000 18:26:51 +0200:
Is it really important for you to be able to use variables?
Yes. We symlink a number of source files to the build directory. The
number of files may vary for different targets. The source file name
varies depending on what's found; we look in target-specific
directories for ``best available'' source files where the filename
extension determines their ``bestness'' (.asm, .S, .s, .c).
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.
I see. Could we have a fourth optional parameter to AC_CONFIG_LINKS
specifying that $1 is a shell variable to be evaluated? Of course,
you won't get dependency tracking for these link/file-pairs in this
case.
Is it enough to be able to
if ...
AC_CONFIG_LINK(foo:bar)
else
AC_CONFIG_LINK(foo:baz)
fi
?
It would be possible if we had some tool generating configure.in for
us. Maybe autoconfconf could read configure.in.in... :-)
--linus
