e6b050212c
-- c2e2e2b21c3fe59b63279e7418c93c7289ee3e27 by Mark Barolak <mbar@google.com>: Import of CCTZ from GitHub. PiperOrigin-RevId: 256220326 -- 3996b01f0c3eb60f72825b154dce8019b6215f1d by Derek Mauro <dmauro@google.com>: Add GCC 4.9 test script. This will become our new minumum version and GCC 4.8 will be removed soon. PiperOrigin-RevId: 256160891 -- 2c13aa44bc8e497ebae9abe8b8adf73c2152622d by Abseil Team <absl-team@google.com>: [Trivial] tweak flat_hash_map.h doc comment The comment is probably right both ways, but the lack of an "if" here seemed jarring to me. PiperOrigin-RevId: 256089069 -- 16bc03b9b30fbf08d7dc61025fa8ec4b57077be8 by Abseil Team <absl-team@google.com>: Fix symbolization for elf files whose SYMTAB section is stripped, but have a DYNSYM section. Previously, if we did not find a SYMTAB section, we would bail out of symbolization early, rather than checking the DYNSYM section. PiperOrigin-RevId: 256061954 -- 4c60ee329b1eeb0b0d10c4f76f282e5fbae2c5b2 by Derek Mauro <dmauro@google.com>: Update to LLVM r363242 and Bazel 0.27.0 PiperOrigin-RevId: 256024405 -- 18e1ba970d33f122026803d8ca90035b9088949d by Eric Fiselier <ericwf@google.com>: Disable variant tests that break with P0608R3 PiperOrigin-RevId: 255975764 -- 0a89858464977e86096b62476faa3b64eb94aa1d by Abseil Team <absl-team@google.com>: Internal change PiperOrigin-RevId: 255891019 -- 9b7424cac66f5407f0ed74ed288bf3099a4fa330 by CJ Johnson <johnsoncj@google.com>: Updates the implementation of InlinedVector::insert(...) to be exception safe and adds an exception safety tests for insert(...) PiperOrigin-RevId: 255881809 -- 1288f4ba3883c510d92b09437fb8b051c19aa241 by CJ Johnson <johnsoncj@google.com>: Updates the implementation of InlinedVector::insert(...) to be exception safe and adds an exception safety tests for insert(...) PiperOrigin-RevId: 255875277 -- 39c04f3621491eaff9e2eda619718d5b5f20fbd9 by Abseil Team <absl-team@google.com>: Use a typedef to allow building with NVCC Without this change NVCC fails to compile compressed_tuple.h. NVCC is relevant because TensorFlow uses NVCC on Ubuntu and inclues abseil. PiperOrigin-RevId: 255850176 -- e23f0309ccad69eb508ca02c9034cd4cdd740da0 by Abseil Team <absl-team@google.com>: Internal change PiperOrigin-RevId: 255787167 -- 054aafcebf595077054164f1da3703124ab209b4 by Abseil Team <absl-team@google.com>: Updates the ScopedAllocatorWorks test for InlinedVector to not rely on the byte count allocated by the standard library In doing so, removes LegacyNextCapacityFrom(...) impl function from InlinedVector Also applies clang-format to the test file PiperOrigin-RevId: 255760356 -- eb05fc9f78e3a163c93f1866e9fe9a8ad0d01622 by Abseil Team <absl-team@google.com>: Internal change PiperOrigin-RevId: 255706834 -- 97abb824417604c45d9fcbb3e4ff1aa3000836f2 by Jorg Brown <jorg@google.com>: Enhance compatibility of abseil's strings package with nvcc. PiperOrigin-RevId: 255688500 -- efc5b9c221ee31e15d10b35d31c8f3ae6eddaa8c by Abseil Team <absl-team@google.com>: Follow CCTZ's lead and allow GetWeekday() and GetYearDay() to be called with any civil-time type. A CivilSecond, for example, has a weekday just as much as a CivilDay does. PiperOrigin-RevId: 255659840 -- a75acbe954457919d8c6c8f4c2339b543760b375 by Derek Mauro <dmauro@google.com>: Increase the timeout of randen_engine_test. It seems to timeout under TSAN often enough to justify the increase. PiperOrigin-RevId: 255628086 -- 160976ba47c7c6eb57af08e21f8eb640aa51e91b by Derek Mauro <dmauro@google.com>: Update CMake documentation Fixes https://github.com/abseil/abseil-cpp/issues/332 PiperOrigin-RevId: 255607313 GitOrigin-RevId: c2e2e2b21c3fe59b63279e7418c93c7289ee3e27 Change-Id: Iba4ac7ed23cbcdb22965b4958601f689be92cda4
99 lines
3.4 KiB
Markdown
99 lines
3.4 KiB
Markdown
# Abseil CMake Build Instructions
|
|
|
|
Abseil comes with a CMake build script ([CMakeLists.txt](../CMakeLists.txt))
|
|
that can be used on a wide range of platforms ("C" stands for cross-platform.).
|
|
If you don't have CMake installed already, you can download it for free from
|
|
<https://www.cmake.org/>.
|
|
|
|
CMake works by generating native makefiles or build projects that can
|
|
be used in the compiler environment of your choice.
|
|
|
|
For API/ABI compatibility reasons, we strongly recommend building Abseil in a
|
|
subdirectory of your project or as an embedded dependency.
|
|
|
|
## Incorporating Abseil Into a CMake Project
|
|
|
|
The recommendations below are similar to those for using CMake within the
|
|
googletest framework
|
|
(<https://github.com/google/googletest/blob/master/googletest/README.md#incorporating-into-an-existing-cmake-project>)
|
|
|
|
### Step-by-Step Instructions
|
|
|
|
1. If you want to build the Abseil tests, integrate the Abseil dependency
|
|
[Google Test](https://github.com/google/googletest) into your CMake project. To disable Abseil tests, you have to pass
|
|
`-DBUILD_TESTING=OFF` when configuring your project with CMake.
|
|
|
|
2. Download Abseil and copy it into a subdirectory in your CMake project or add
|
|
Abseil as a [git submodule](https://git-scm.com/docs/git-submodule) in your
|
|
CMake project.
|
|
|
|
3. You can then use the CMake command
|
|
[`add_subdirectory()`](https://cmake.org/cmake/help/latest/command/add_subdirectory.html)
|
|
to include Abseil directly in your CMake project.
|
|
|
|
4. Add the **absl::** target you wish to use to the
|
|
[`target_link_libraries()`](https://cmake.org/cmake/help/latest/command/target_link_libraries.html)
|
|
section of your executable or of your library.<br>
|
|
Here is a short CMakeLists.txt example of a project file using Abseil.
|
|
|
|
```cmake
|
|
cmake_minimum_required(VERSION 3.5)
|
|
project(my_project)
|
|
|
|
# Pick the C++ standard to compile with.
|
|
# Abseil currently supports C++11, C++14, and C++17.
|
|
set(CMAKE_CXX_STANDARD 11)
|
|
|
|
add_subdirectory(abseil-cpp)
|
|
|
|
add_executable(my_exe source.cpp)
|
|
target_link_libraries(my_exe absl::base absl::synchronization absl::strings)
|
|
```
|
|
|
|
### Running Abseil Tests with CMake
|
|
|
|
Use the `-DABSL_RUN_TESTS=ON` flag to run Abseil tests. Note that if the `-DBUILD_TESTING=OFF` flag is passed then Abseil tests will not be run.
|
|
|
|
You will need to provide Abseil with a Googletest dependency. There are two
|
|
options for how to do this:
|
|
|
|
* Use `-DABSL_USE_GOOGLETEST_HEAD`. This will automatically download the latest
|
|
Googletest source into the build directory at configure time. Googletest will
|
|
then be compiled directly alongside Abseil's tests.
|
|
* Manually integrate Googletest with your build. See
|
|
https://github.com/google/googletest/blob/master/googletest/README.md#using-cmake
|
|
for more information on using Googletest in a CMake project.
|
|
|
|
For example, to run just the Abseil tests, you could use this script:
|
|
|
|
```
|
|
cd path/to/abseil-cpp
|
|
mkdir build
|
|
cd build
|
|
cmake -DABSL_USE_GOOGLETEST_HEAD=ON -DABSL_RUN_TESTS=ON ..
|
|
make -j
|
|
ctest
|
|
```
|
|
|
|
Currently, we only run our tests with CMake in a Linux environment, but we are
|
|
working on the rest of our supported platforms. See
|
|
https://github.com/abseil/abseil-cpp/projects/1 and
|
|
https://github.com/abseil/abseil-cpp/issues/109 for more information.
|
|
|
|
### Available Abseil CMake Public Targets
|
|
|
|
Here's a non-exhaustive list of Abseil CMake public targets:
|
|
|
|
```cmake
|
|
absl::base
|
|
absl::algorithm
|
|
absl::debugging
|
|
absl::flat_hash_map
|
|
absl::memory
|
|
absl::meta
|
|
absl::numeric
|
|
absl::strings
|
|
absl::synchronization
|
|
absl::time
|
|
absl::utility
|
|
```
|