[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: gnulib build/test ?
From: |
Tim Rühsen |
Subject: |
Re: gnulib build/test ? |
Date: |
Tue, 16 May 2017 16:55:15 +0200 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 |
Oh, just realized that ChangeLog has to be manually edited.
Here is the amended patch.
With Best Regards, Tim
On 05/16/2017 03:52 PM, Tim Rühsen wrote:
> Bruno ! You saved my day !
>
>
> I put your description with some small amendments into the README.
> Here's the patch.
>
>
> With Best Regards, Tim
>
>
>
> On 05/16/2017 03:17 PM, Bruno Haible wrote:
>> Hi Tim,
>>
>>> Not sure how to build and run the test suite. The README just points me
>>> to a .texi file which is hardly readable, at least I get a headache
>>> after ~10s.
>>
>> I agree. The README should better say to
>> $ cd doc
>> $ make gnulib.html
>> $ xdg-open gnulib.html
>> or read the manual at
>> https://www.gnu.org/software/gnulib/manual/gnulib.html
>>
>>> What else should I try to build + run the test suite ?
>>
>> You first pick a subset of the Gnulib modules, that you want to work on.
>> Then you create a testdir for these modules:
>>
>> $ ./gnulib-tool --create-testdir --dir=../testdir1 --single-configure
>> MODULE1 [MODULE2...]
>>
>> This testdir is something you can "./configure CPPFLAGS=-Wall && make &&
>> make check".
>>
>> For the set of Gnulib modules:
>> - If you don't specify any, it defaults to *all*!
>> - There is a script 'posix-modules' that returns the POSIX related
>> modules. Use like this:
>> $ ./gnulib-tool --create-testdir --dir=../testdir-posix
>> --single-configure `./posix-modules`
>>
>> Note the difference between --dir=../testdir1 and --dir=/tmp/testdir1 : The
>> former is on the
>> same file system as the gnulib checkout, and uses hard links to the .c and
>> .h files; therefore
>> for quick edits of only .h and .c files you can do the edits in the testdir,
>> test them
>> through "make" and "make check", and will usually find them present in the
>> gnulib clone.
>> In the second case, or when you start to edit .m4 files or module
>> descriptions, it's useful
>> to work in the gnulib clone, and repeatedly rerun the commands:
>> $ ./gnulib-tool --create-testdir --dir=../testdir2 --single-configure
>> MODULE1 [MODULE2...]
>> $ cd ../testdir2
>> $ ./configure CPPFLAGS=-Wall && make && make check
>>
>> Bruno
>>
>>
0001-README-Add-notes-for-first-time-contributors.patch
Description: Text Data
signature.asc
Description: OpenPGP digital signature
- gnulib build/test ?, Tim Rühsen, 2017/05/16
- Re: gnulib build/test ?, Bruno Haible, 2017/05/16
- Re: gnulib build/test ?, Tim Rühsen, 2017/05/16
- Re: gnulib build/test ?,
Tim Rühsen <=
- Re: gnulib build/test ?, Bruno Haible, 2017/05/17
- Re: gnulib build/test ?, Tim Rühsen, 2017/05/17
- gnulib-tool: don't use hard links, Bruno Haible, 2017/05/20
- Re: gnulib-tool: don't use hard links, Paul Eggert, 2017/05/20
- Re: gnulib-tool: don't use hard links, Bruno Haible, 2017/05/21
- Re: gnulib-tool: don't use hard links, Paul Eggert, 2017/05/21
- Re: gnulib-tool: don't use hard links, Bruno Haible, 2017/05/21
- Re: gnulib-tool: don't use hard links, Bruno Haible, 2017/05/21
- Re: gnulib-tool: don't use hard links, Paul Eggert, 2017/05/21