Simon Josefsson wrote:
> > 2) Transfer this directory to a build machine (HP-UX, Cygwin, or
> > whatever).
>
> Step 2 can be simplified by doing:
>
> ./configure
> make dist
>
> since gnulib-tool already create a dummy configure.ac that
> AC_CONFIG_SUBDIR include every gnulib module. Running
Bruno Haible <[EMAIL PROTECTED]> writes:
> The use of this facility is as follows:
> 1) On a machine with recent automake, autoconf, m4 installed and with a
> gnulib cvs checkout (typically a Linux machine), use
> "gnulib-tool --create-megatestdir --dir=..."
> Note: The created
Simon Josefsson wrote:
> Should --create-megatestdir add this automatically?
I'd say, better keep it optional. Although currently I use --with-tests always,
there are cases when one cares whether the code compiles in the first place,
ignoring the tests.
Bruno
Bruno Haible <[EMAIL PROTECTED]> writes:
> "gnulib-tool --create-megatestdir --dir=..."
Don't forget to add --with-tests too.
Should --create-megatestdir add this automatically?
/Simon
Bruno Haible <[EMAIL PROTECTED]> writes:
> Simon's http://autobuild.josefsson.org/gnulib/ summary page could be more
> useful (and larger :-)) if more people submit test results. To this
> effect, I'm adding a facility that produces an 'autobuild' script in
> "gnulib-tool --create-megatestdir".
N
Simon's http://autobuild.josefsson.org/gnulib/ summary page could be more
useful (and larger :-)) if more people submit test results. To this
effect, I'm adding a facility that produces an 'autobuild' script in
"gnulib-tool --create-megatestdir".
The use of this facility is as follows:
1) On a m
