From: David Kalnischkies <david@kalnischkies.de>
Date: Sun, 13 Apr 2014 19:40:35 +0000 (+0200)
Subject: compile with absolute paths to allow lcov use
X-Git-Tag: 1.0.2~3^2~5
X-Git-Url: https://git.saurik.com/apt.git/commitdiff_plain/cbc9ec23b0fb551f20f4fd8ca46d98f59b5666bc?hp=cbc9ec23b0fb551f20f4fd8ca46d98f59b5666bc

compile with absolute paths to allow lcov use

Instructing gcc (or clang) to prepare for capturing coverage data is
easy: Just build with: CXXFLAGS=--coverage

The hard part is that our buildsystem uses relative paths and so
confuses the hell out of lcov as it assumes this way that all our *.cc
files are in the same directory… by changing to absolute paths in the
compile rules we solve this problem.

Still not perfect as it refers to build/include files for most headers
and our forking/threading code isn't properly captured, but good enough
to see red reports for now:

CXXFLAGS=--coverage make
make test
./test/integration/run-tests -q
lcov --no-external --directory . --capture --output-file apt.info
genhtml --output-directory ./coverage/ apt.info

Git-Dch: Ignore
---