summaryrefslogtreecommitdiff
path: root/debian/rules
Commit message (Collapse)AuthorAge
* Reenable unit tests on mips64elGravatar Benjamin Barenblat2021-06-13
|
* Reenable unit tests on arm64Gravatar Benjamin Barenblat2021-04-16
|
* Request that tests get builtGravatar Benjamin Barenblat2021-04-08
| | | | | Abseil now requires -DBUILD_TESTS=ON instead of -DABSL_RUN_TESTS=ON. Make the appropriate replacement in debian/rules.
* Reenable unit tests on ppc64elGravatar Benjamin Barenblat2021-03-05
|
* Re-disable unit tests on non-amd6420200923.2-3Gravatar Benjamin Barenblat2021-01-31
| | | | | | I’m still working to fix unit tests on non-amd64 platforms, but this package needs to migrate. Disable unit tests everywhere they don’t work.
* Avoid OOM on mipsel buildds by disabling unit tests thereGravatar Benjamin Barenblat2021-01-31
|
* Reenable unit tests20200923.2-2Gravatar Benjamin Barenblat2020-12-01
| | | | | | | | | | | | | Now that https://bugs.debian.org/970943 has been resolved and a new Git snapshot of googletest has made it to testing, reenable Abseil unit tests and run them as part of the build process. This does not change the package as viewed by dependents; it only provides greater assurance of correctness when an upload occurs. (It probably would have caught http://bugs.debian.org/973492, for instance.) Run the tests against the shared libraries, not the static ones, to more accurately simulate the conditions under which dependents are likely to use Abseil.
* Switch to shlibs infrastructureGravatar Benjamin Barenblat2020-07-24
| | | | | | | | | | Remove the symbols file and replace it with an shlibs file. Since Abseil is almost certain to break ABI with every release, maintaining fine-grained symbol histories is not terribly useful anyway; furthermore, since Abseil is a C++ library, maintaining a symbols file is a lot of work. Bug: https://bugs.debian.org/966183
* Rework symbols file for GCC 9 using pkg-kde-toolsGravatar Benjamin Barenblat2020-07-23
| | | | | | | | Rebuild abseil against GCC 9, the version currently in unstable, and update the symbols file. Additionally, rework the symbols file using pkg-kde-tools, which offers some automation for building large symbols files. This does mean that the symbols file now contains mangled names, but it’s still easily inspected through c++filt.
* Pass -ffile-prefix-map during the buildGravatar Benjamin Barenblat2020-05-22
| | | | | Abseil uses __FILE__ in error messages. Ensure that that macro expands to the same value on every builder by passing -ffile-prefix-map to GCC.
* Build static librariesGravatar Benjamin Barenblat2020-05-22
| | | | | | | | | | | | | | Build archives in addition to shared objects for Abseil code. Build the shared objects after the archives so that files autogenerated during the build (like CMake support files) reference the shared objects, not the archives. This ensures that users get shared objects by default; this is the common case in Debian, and it also helps prevent ODR violations caused by double-linking an archive. This patch is heavily based on one provided in <CAKjSHr2qpxgDcnRVoYCptVytTy-QjXy38AM4ppSKv1noXOGjwg@mail.gmail.com> by László Böszörményi (GCS) <gcs@debian.org>; it’s available on the web at https://bugs.debian.org/888705#150.
* Enable CMake supportGravatar Benjamin Barenblat2020-05-19
| | | | | | | Install Abseil’s CMake support files. Some of these files are autogenerated, and the generator produces files with a googletest dependency if Abseil is built with unit tests enabled; to prevent this, turn off unit tests.
* Start packaging AbseilGravatar Benjamin Barenblat2020-05-18
Create basic packaging for Abseil. There’s still work to be done – there are no autopkgtests, and this package doesn’t install Abseil’s CMake integration. However, you can install the binary packages and build programs that link the libraries.