Hello Simon, Bruno,
* Simon Josefsson wrote on Mon, May 11, 2009 at 12:44:08PM CEST:
> Bruno Haible writes:
> > gnulib-tool searches for all gnulib directories only when no --m4-base
> > option was specified.
>
> That is what caused this problem -- what do you think about making
> gnulib-tool av
Bruno Haible writes:
> Simon Josefsson wrote:
>> No, I just invoke 'gnulib-tool --import' once in the top-level
>> directory. Gnulib-tool notices the gnulib directories beneath lib/ as
>> well, and will import files to lib/. ...
>>
>> How do I stop gnulib-tool from importing gnulib files in li
Simon Josefsson wrote:
> No, I just invoke 'gnulib-tool --import' once in the top-level
> directory. Gnulib-tool notices the gnulib directories beneath lib/ as
> well, and will import files to lib/. ...
>
> How do I stop gnulib-tool from importing gnulib files in lib/, so I can
> invoke gnulib-t
Bruno Haible writes:
> Simon Josefsson wrote:
>> However, gnulib-tool --import puts build-aux files in the wrong
>> directory for the lib/gl/m4 base. The reason is because the --auxdir
>> variable is read from the top-level configure.ac AC_CONFIG_AUX_DIR.
>>
>> One work around is to run gnulib-
Bruno Haible writes:
> The same thing will also work without the conditional branches. I'm
> applying this:
>
> 2009-05-10 Bruno Haible
>
> * gnulib-tool (func_import, func_create_testdir, copy-file): Change
> sed_rewrite_old_files, sed_rewrite_new_files, sed_rewrite_files so that
Ralf Wildenhues wrote:
> > >sed_rewrite_old_files="\
> > > +s,^lib/,$cached_sourcebase/,
> > > s,^build-aux/,$auxdir/,
> > > s,^doc/,$cached_docbase/,
> > > -s,^lib/,$cached_sourcebase/,
> > > s,^m4/,$cached_m4base/,
> > > s,^tests/,$cached_testsbase/,
> > > s,^
Hi Bruno,
* Bruno Haible wrote on Sat, May 09, 2009 at 03:12:01AM CEST:
> Ralf Wildenhues wrote:
>
> > why can't your two configure.ac scripts share a
> > build-aux directory? The toplevel one could have
> > AC_CONFIG_AUX_DIR([lib/build-aux])
> >
> > while lib/configure.ac had
> > AC_CONFIG_
Simon Josefsson wrote:
> However, gnulib-tool --import puts build-aux files in the wrong
> directory for the lib/gl/m4 base. The reason is because the --auxdir
> variable is read from the top-level configure.ac AC_CONFIG_AUX_DIR.
>
> One work around is to run gnulib-tool --import two times
Yes,
Ralf Wildenhues writes:
> Hi Simon,
>
> * Simon Josefsson wrote on Thu, May 07, 2009 at 01:01:42PM CEST:
>>
>> My thought is that the machinery to search top-level configure.ac for
>> AC_CONFIG_AUX_DIR is not worth the trouble, and that we should use the
>> same machinery for specifying the othe
Hi Simon,
* Simon Josefsson wrote on Thu, May 07, 2009 at 01:01:42PM CEST:
>
> My thought is that the machinery to search top-level configure.ac for
> AC_CONFIG_AUX_DIR is not worth the trouble, and that we should use the
> same machinery for specifying the other directories to gnulib-tool for
>
In GNU SASL I have one top-level configure.ac (for command line tools,
self-tests, etc) and one lib/configure.ac (for the library). There is
one gnulib m4-base in gl/m4 and one in lib/gl/m4. Both top-level and
lib/ import the maintainer-makefile module, which is needed for
downloading translation
11 matches
Mail list logo
