Hi, [EMAIL PROTECTED] (Ludovic Courtès) writes:
> Ralf Wildenhues <[EMAIL PROTECTED]> 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'. Actually, it just occurred to me that `AC_CONFIG_LINKS' doesn't work here when builddir != srcdir, because both the source and destination of the link (namely `some-special-name.h' and `config.h') are under builddir, whereas `AC_CONFIG_LINKS' looks for the source file under `srcdir'. Preparing by hand a `config.h' or `config.h.in' and putting it under `lib' doesn't work either because it would not get included in the distribution (I suspect). Modifying by hand the Gnulib-generated `lib/Makefile.am' doesn't seem like a viable option either. Am I overlooking possible solutions or do I really have to rename `some-special-name.h' to `config.h'? Thanks, Ludovic.
