Paul Eggert <[EMAIL PROTECTED]> wrote:
> Jim Meyering <[EMAIL PROTECTED]> writes:
>
>> However, I can't reproduce that:
>>
>> $ git clone git://git.sv.gnu.org/coreutils.git cu \
>> && cd cu && ./bootstrap --gnulib-srcdir=/gnulib
>> ...
>> Creating ./._bootmp/lib/uniwidth/.gitignor
Hi,
I just noticed that Gnulib modules rely on the availability of a
`#include'able file.
I'm using Gnulib in a project that does:
AC_CONFIG_HEADER([some-special-name.h])
There, Gnulib modules fail to compile because is not
available. I'd happily work around this by doing something like:
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
#incl
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Since the use of gnulib has the tendency to introduce translatable strings
into a project, should there be a way for gnulib-tool to mark which files
need to be added to POTFILES.in? Perhaps a new entry in each module
description that calls out any fil
-BEGIN PGP SIGNED MESSAGE-
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
