Hello Ludovic,
* Ludovic Courtès wrote on Tue, Aug 28, 2007 at 02:32:12PM CEST:
> [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
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 en
On 7/22/07, Ralf Wildenhues <[EMAIL PROTECTED]> wrote:
Hello James,
* James Youngman wrote on Sat, Jul 21, 2007 at 11:34:42PM CEST:
>
> My rationale is that the big-lost-of-things-to-do works fine for
> first-time adopters, but for those who routinely run it, there is no
> sense of incremental c
Hello James,
* James Youngman wrote on Sat, Jul 21, 2007 at 11:34:42PM CEST:
>
> My rationale is that the big-lost-of-things-to-do works fine for
> first-time adopters, but for those who routinely run it, there is no
> sense of incremental change; there's no easy way of noticing that an
> extra r
On 7/18/07, Ludovic Courtès <[EMAIL PROTECTED]> wrote:
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."
I vote against adding more such messages. gnulib-tool al
Hi,
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'
li
-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
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
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:
