Eric Blake wrote:
> Personally, I use:
>
> ./gnulib-tool --with-tests --test copy-file
>
> which says to include the copy-file-tests module automatically, as well
> as running the unit test (and clean it up on success), when developing
> on a single machine. And when trying to test on a machine
Reuben Thomas wrote:
> Oh wait…
>
> ./gnulib-tool --test --dir=/tmp/testdir --with-tests copy-file-tests
>
> seems to do what I want! Still, this is not exactly obvious.
Hope this patch will make it a little bit more obvious.
2012-01-10 Bruno Haible
doc: Mention --with-tests option
On 10 January 2012 18:14, Reuben Thomas wrote:
>>
>> It is good practice when asking for help (and getting it)
>> to volunteer the patch that would have saved you some trouble.
>> Since you've just hit a particular problem you are perhaps better
>> placed than anyone else to propose a fix.
You've
On 10 January 2012 18:07, Jim Meyering wrote:
>
> It is good practice when asking for help (and getting it)
> to volunteer the patch that would have saved you some trouble.
> Since you've just hit a particular problem you are perhaps better
> placed than anyone else to propose a fix.
You're quite
Reuben Thomas wrote:
> On 10 January 2012 16:58, Eric Blake wrote:
>>
>> Yes, --dir is optional if you don't specify --create-testdir.
>
> Right, so could you please fix the documentation accordingly?
Hi Reuben,
It is good practice when asking for help (and getting it)
to volunteer the patch tha
On 10 January 2012 16:58, Eric Blake wrote:
>
> Yes, --dir is optional if you don't specify --create-testdir.
Right, so could you please fix the documentation accordingly?
Correcting the help of gnulib-tool seems to be sufficient, since the
--test option is not documented in the manual (at least,
On 01/10/2012 09:55 AM, Reuben Thomas wrote:
>> That says where the test dir should be located, but didn't load any test
>> modules to actually do the testing. Personally, I use:
>>
>> ./gnulib-tool --with-tests --test copy-file
>>
>> which says to include the copy-file-tests module automatically,
On 10 January 2012 16:51, Eric Blake wrote:
> On 01/10/2012 09:30 AM, Reuben Thomas wrote:
>> I've just spent a while trying to work out how to run tests for a
>> particular module, and I'm not getting very far.
>>
>> ./gnulib-tool --help brings up the "--test" mode, which looks
>> promising, but
On 01/10/2012 09:30 AM, Reuben Thomas wrote:
> I've just spent a while trying to work out how to run tests for a
> particular module, and I'm not getting very far.
>
> ./gnulib-tool --help brings up the "--test" mode, which looks
> promising, but if I run
>
> ./gnulib-tool --test --test-dir=/tmp/
I've just spent a while trying to work out how to run tests for a
particular module, and I'm not getting very far.
./gnulib-tool --help brings up the "--test" mode, which looks
promising, but if I run
./gnulib-tool --test --test-dir=/tmp/testdir copy-file
then that only seems to build copy-file,
10 matches
Mail list logo
