Re: coreutils test coverage

[Jim Meyering]

Bo Borgerson <address@hidden> wrote:
> Daniel Dunbar wrote:
>> Here is the process I use for generating those results. First, generate the
>> coverage information:
>
> Thanks, that worked like a charm!
>
> I've attached a patch that puts your instructions into the HACKING file.

Thanks!  Applied.

> I used a `.lcov' extension for the lcov output files instead of `.info',
> since that extension is already used in the doc/ directory for a
> different file format.
>
> One nice further addition would be to have `make clean' also remove the

Good idea.  However, "make clean" only removes things created by
"make some-target", so you'd need ...

> generated `.gcda' and `.gcno' files, but I'm going to show my
> inexperience here and say I don't know how to do that safely. :)

Better still would be to add a Makefile target to do what
those rules say.  Then HACKING can simply suggest to run "make lcov".