summaryrefslogtreecommitdiff
path: root/buildlib/python.mak
Commit message (Collapse)AuthorAgeFilesLines
* Get rid of the old buildsystemJulian Andres Klode2016-08-101-68/+0
| | | | Bye, bye, old friend.
* buildsystem: deal with spaces in path to sourceDavid Kalnischkies2015-12-191-1/+1
| | | | Git-Dch: Ignore
* move -std=c++11 from CXX to new CXXSTDDavid Kalnischkies2015-11-191-2/+2
| | | | | | | | 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 useDavid Kalnischkies2014-04-131-1/+1
| | | | | | | | | | | | | | | | | | | | | | 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 aliencodeArch Librarian2004-09-201-0/+68
Author: jgg Date: 2001-02-20 07:03:16 GMT Join with aliencode