apt/buildlib/library.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
change to libapt-pkg abi 5.0 with versioned symbols2015-08-10T15:27:59ZDavid Kalnischkiesdavid@kalnischkies.de2015-08-10T09:08:35Zurn:sha1:ae97af1fdf726a0e7e553b2fb5734b6e09a088d0
We changed an aweful lot of stuff, so 5.0 is properly better than 4.X as
a semantic version and as we are at it lets add some trivial symbol
versioning as well: We just mark all exported symbols with the same
version for now. This isn't really the proper thing to do as if we add
symbols in later versions (with the same abi) they will get the same
symbols version, but our .symbols file will protect us from the problems
arising from this as it will ensure that a package acutally depends on a
version of the abi high enough to include the symbol.
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
depend on libapt-pkg in the libapt-inst build process2013-06-09T13:12:32ZDavid Kalnischkieskalnischkies@gmail.com2013-05-28T16:48:28Zurn:sha1:564fcbf93c78deb48fa44a9a63b5602eedfa53a9
fixing parallel build in the handcrafted buildsystem is a pain,
so its not enabled by default, but its works for me – sometimes
Git-Dch: Ignore
we break the ABI, so let use increase the ABI number :)2010-02-18T00:37:59ZDavid Kalnischkieskalnischkies@gmail.com2010-02-18T00:37:59Zurn:sha1:44c8b5dff8871485d071f92cd154dc1c14c3c015
(This is the revert of the glibc-abi-compatibility-hack)
revert this commit as fast as possible (aka next ABI break)2009-12-12T00:54:33ZDavid Kalnischkieskalnischkies@gmail.com2009-12-12T00:54:33Zurn:sha1:c0a73937424fa427972835342f12f5fbaa6d0c88
This commit sets up our faked library extension to trick the build
system into building the packages with libc6.9-6 while we are actually
already at libc6.10-6. Oh dear...
Bumped libapt version and excluded eglibc from SONAME. (Closes: #448249)2009-10-24T15:38:06ZDavid Kalnischkieskalnischkies@gmail.com2009-10-24T15:38:06Zurn:sha1:10c9f030e02ccec5c002abc42776f994c124c574
Backported from lp:~mvo/apt/debian-experimental
Based on patch by Eugene V. Lyubimkin
s/DOMAIN/APT_DOMAIN/, as /usr/include/math.h defines DO...2004-09-20T16:59:58ZArch Librarianarch@canonical.com2004-09-20T16:59:58Zurn:sha1:c6e8074f628eb380883dd3b0cbdc60eb7ef6d0f5
Author: doogie
Date: 2002-11-11 07:00:16 GMT
s/DOMAIN/APT_DOMAIN/, as /usr/include/math.h defines DOMAIN to 1, and
breaks us.
gettext stuff2004-09-20T16:59:33ZArch Librarianarch@canonical.com2004-09-20T16:59:33Zurn:sha1:809484570008da67b0dcd291af7673481fff52f6
Author: jgg
Date: 2002-10-16 05:24:02 GMT
gettext stuff