[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Reliance on <config.h>

From: Ralf Wildenhues
Subject: Re: Reliance on <config.h>
Date: Wed, 18 Jul 2007 00:40:02 +0200
User-agent: Mutt/1.5.13 (2006-08-11)

Hello Ludovic,

* Ludovic Courtès wrote on Tue, Jul 17, 2007 at 05:58:34PM CEST:
>   AC_CONFIG_HEADERS([some-special-name.h lib/config.h])
> but then `autoheader' does not generate `lib/config.h.in', which is a
> pain.

You could either write lib/config.h.in yourself; it could contain
  #include "some-special-name.h"

(also, you could just use a file lib/config.h -- there are no #defines
that are changed by configure).

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.

(I suppose another gnulib-specific possibility is that someone hacks
gnulib-tool to support arbitrary other configuration header file names;
or to undo the decision that was made last year to assume a config.h
header file.)

Hope that helps.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]