Re: improving lcov reports

Hi Stefan,

I've reviewing this and you're definitely right. Your workaround works
well for us too so I'll put this in b.g.o as soon as I can.

Btw, $(PWD) may have some problems, for example in my case the work dir
is symlinked (this is $PWD shows a path through symlinks) but the .info
files contains the real paths to files. As result, nothing gets
extracted from the info file when I use $PWD with the --extract option
unless I accessed the workdir through the real path to avoid symlinks.
To get rid of this I just used "pwd -P" instead:

lcov --extract ./coverage/$(PACKAGE) "`pwd -P`/*"
-o ./coverage/$(PACKAGE).info 

Thanks for your hint!


On Wed, 2007-08-01 at 20:05 +0300, Stefan Kost wrote:
> hi,
> I just looked at this coverage report:
> imho lcov has a bug to include other sources/include in the report, but I've got
> a workaround from the lcov developers
> I wonder if and where we can use this for
> here is how I filter the lcov output (lcov --extract)
> coverage::
> 	mkdir -p ./coverage
> 	lcov --directory . --zerocounters
> 	-$(MAKE) check
> 	lcov --directory ./src --capture --output-file ./coverage/$(PACKAGE)
> 	lcov --extract ./coverage/$(PACKAGE) "$(PWD)/src*" -o
> ./coverage/$(PACKAGE).info
> 	$(RM) ./coverage/$(PACKAGE)
> 	genhtml -o ./coverage --num-spaces 2 ./coverage/$(PACKAGE).info
> I need to check if $(PWD) works in all cases. I can't use $(top_srcdir) as this
> is relative.
> Stefan
> _______________________________________________
> Build-brigade-list mailing list
> Build-brigade-list gnome org

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]