Re: Reliance on <config.h>

[Ludovic Courtès]

Hi,

Ralf Wildenhues <address@hidden> writes:

> Another possibility is to generate lib/config.h.in from
> some-special-name.h.in, say, by some sed script or an autoheader
> invocation with arguments and output redirection.

Good point.  I ended up using `AC_CONFIG_LINKS' to have a `config.h'
linked to `some-special-name.h'.

Eric Blake <address@hidden> writes:

> I think it will be easier for you to provide a stub lib/config.h than to
> try and restore all the sed invocations into gnulib-tool to convert to
> your custom name at checkout, not to mention that gnulib-tool is already
> slow enough as it is.

Possibly.  Still, that is one of the few things that doesn't work
automagically with Gnulib, so it's quite surprising at first.  ;-)

Alternatively, maybe `gnulib-tool --import' should say something like
"Make sure `lib/config.h' is available, e.g., by adding
`AC_CONFIG_LINKS(bla bla)' to your `configure.ac' file."

Thanks,
Ludovic.