apt/buildlib/python.mak, branch 1.2.7Debians commandline package managerhttps://git.kalnischkies.de/apt/atom?h=1.2.72015-12-19T22:04:34Zbuildsystem: deal with spaces in path to source2015-12-19T22:04:34ZDavid Kalnischkiesdavid@kalnischkies.de2015-12-15T16:18:50Zurn:sha1:85a67355c0340596630a47f85507d61c68dcbd0e
Git-Dch: Ignore
move -std=c++11 from CXX to new CXXSTD2015-11-19T18:27:09ZDavid Kalnischkiesdavid@kalnischkies.de2015-11-19T18:27:09Zurn:sha1:c3c77d09651b5bed315c83ebe2354c9d2cb31253
The hack introduced in aa91826f is replaced with a hopefully better
working "proper" solution with a new variable just for the standard we
use everywhere we use CXXFLAGS.
Git-Dch: Ignore
compile with absolute paths to allow lcov use2014-04-13T20:12:01ZDavid Kalnischkiesdavid@kalnischkies.de2014-04-13T19:40:35Zurn:sha1:cbc9ec23b0fb551f20f4fd8ca46d98f59b5666bc
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
Join with aliencode2004-09-20T16:56:32ZArch Librarianarch@canonical.com2004-09-20T16:56:32Zurn:sha1:b2e465d6d32d2dc884f58b94acb7e35f671a87fe
Author: jgg
Date: 2001-02-20 07:03:16 GMT
Join with aliencode