Re: config.status usage

[Akim Demaille <akim at epita dot fr>]

>>>>> "Lars" == Lars J Aas <larsa@sim.no> writes:

Lars> This will produce out.tmp in $(builddir), but expect out.tmp to
Lars> be in $(srcdir) for the second pass, wouldn't it?  Any hints on
Lars> what the best workaround to that small obstacle is?

You're right, grmph.  I don't how to handle this, unless we equip
config.status with support for absolute paths for input files...
Maybe there's a way with CONFIG_LINKS, but it getting even dirtier :(

Maybe you can try to use CONFIG_COMMANDS here, but it puke puke
puke...

AC_CONFIG_COMMANDS(output,
[./config.status --header output.tmp:output.in
cp output.tmp $srcdir
./config.status --file output:output.tmp])

But it violate the read-only srcdir.  I once wondered whether it'd be
useful to be able to pipe into ./config.status, this would be one
instance.

The biggest problem is that config.status uselessly won't let you have
a src file with an absolute path:

~/src/textutils % CONFIG_HEADERS="output:/tmp/out.$$" CONFIG_FILES="/tmp/out.$$:output.in" ./config.status
creating /tmp/out.984
creating output
configure: error: cannot find input file `.//tmp/out.984'