[Top][All Lists]

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

Re: Reliance on <config.h>

From: Eric Blake
Subject: Re: Reliance on <config.h>
Date: Tue, 17 Jul 2007 22:37:28 -0600
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv: Gecko/20070604 Thunderbird/ Mnenhy/

Hash: SHA1

According to Ralf Wildenhues on 7/17/2007 4:40 PM:
> (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.)

One of the reasons that gnulib moved towards assuming <config.h> is that
it makes for shorter command lines in make output, and it is easier to
write maintainer-check rules that ensure every .c includes <config.h> as
the first line (a necessity if gnulib replaces any system header).  In the
early days of autoconf, it was sufficient to just list lots of -D...
options on the command line, but these days, gnulib defines so many macros
that it is feasible to exceed command line limits on some platforms if you
do not lump them all into a config.h.

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.

- --
Don't work too hard, make some time for fun as well!

Eric Blake             address@hidden
Version: GnuPG v1.4.5 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org


reply via email to

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