| commit | 3187b54c0ca3a17d4de6dfe7aeb37ceab8f1cfae | [log] [tgz] |
|---|---|---|
| author | Tim Van Patten <timvp@google.com> | Wed Sep 23 19:37:49 2020 +0000 |
| committer | Copybara-Service <copybara-worker@google.com> | Wed Sep 23 12:41:57 2020 -0700 |
| tree | 1bf54cf6099b92d9bf848ee59dd8a180a28237b5 | |
| parent | 5c8d9202c95f957efbbe43055a62fd35fd78043b [diff] |
Abseil: Only use Windows .def files with clang The various .def files used in Windows builds are generated using llvm-nm and only support being used with the clang compiler. These .def files can't be used with MSVC, though we are unsure if that's related to how they are generated by generate_def_files.py or how MSVC consumes them (i.e. the format it expects for the symbols). The issue is primarly about the custom libcxx and MSVC's inability to work correctly with it. //build/config/c++/c++.gni handles this automatically by disabling the custom libcxx for non-clang (MSVC) builds by setting use_custom_libcxx = false. However, this causes the .def symbols to be generated differently (incorrectly), causing link failures related to too many symbols being exported. This change helps support using Abseil in ANGLE, particularly standalone component builds built with MSVC. This is a workaround until: 1.) EXPORT macros are used (preferred). OR 2.) generate_def_files.py can generate .def files for both clang and MSVC, either manually or as part of the build (unpreferred, since the script itself is a workaround). Abseil: Only use Windows .def files with clang The various .def files used in Windows builds are generated using llvm-nm and only support being used with the clang compiler. These .def files can't be used with MSVC, though we are unsure if that's related to how they are generated by generate_def_files.py or how MSVC consumes them (i.e. the format it expects for the symbols). The issue is primarly about the custom libcxx and MSVC's inability to work correctly with it. //build/config/c++/c++.gni handles this automatically by disabling the custom libcxx for non-clang (MSVC) builds by setting use_custom_libcxx = false. However, this causes the .def symbols to be generated differently (incorrectly), causing link failures related to too many symbols being exported. This change helps support using Abseil in ANGLE, particularly standalone component builds built with MSVC. This is a workaround until: 1.) EXPORT macros are used (preferred). OR 2.) generate_def_files.py can generate .def files for both clang and MSVC, either manually or as part of the build (unpreferred, since the script itself is a workaround). Bug: 1126524 Test: Manual verification with standalone ANGLE build Change-Id: Icf071635938f83818b8345b38074c21f362b897c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2419155 Commit-Queue: Tim Van Patten <timvp@google.com> Reviewed-by: Jamie Madill <jmadill@chromium.org> Reviewed-by: Bruce Dawson <brucedawson@chromium.org> Reviewed-by: Mirko Bonadei <mbonadei@chromium.org> Cr-Commit-Position: refs/heads/master@{#809901} GitOrigin-RevId: 6e043d67ce7f3ebf27b4809a2d48d65eb05156ef
The repository contains the Abseil C++ library code. Abseil is an open-source collection of C++ code (compliant to C++11) designed to augment the C++ standard library.
Abseil is an open-source collection of C++ library code designed to augment the C++ standard library. The Abseil library code is collected from Google's own C++ code base, has been extensively tested and used in production, and is the same code we depend on in our daily coding lives.
In some cases, Abseil provides pieces missing from the C++ standard; in others, Abseil provides alternatives to the standard for special needs we've found through usage in the Google code base. We denote those cases clearly within the library code we provide you.
Abseil is not meant to be a competitor to the standard library; we've just found that many of these utilities serve a purpose within our code base, and we now want to provide those resources to the C++ community as a whole.
If you want to just get started, make sure you at least run through the Abseil Quickstart. The Quickstart contains information about setting up your development environment, downloading the Abseil code, running tests, and getting a simple binary working.
Bazel is the official build system for Abseil, which is supported on most major platforms (Linux, Windows, macOS, for example) and compilers. See the quickstart for more information on building Abseil using the Bazel build system.
If you require CMake support, please check the CMake build instructions.
Abseil contains the following C++ library components:
base Abseil Fundamentals base library contains initialization code and other code which all other Abseil code depends on. Code within base may not depend on any other code (other than the C++ standard library).algorithm algorithm library contains additions to the C++ <algorithm> library and container-based versions of such algorithms.container container library contains additional STL-style containers, including Abseil's unordered “Swiss table” containers.debugging debugging library contains code useful for enabling leak checks, and stacktrace and symbolization utilities.hash hash library contains the hashing framework and default hash functor implementations for hashable types in Abseil.memory memory library contains C++11-compatible versions of std::make_unique() and related memory management facilities.meta meta library contains C++11-compatible versions of type checks available within C++14 and C++17 versions of the C++ <type_traits> library.numeric numeric library contains C++11-compatible 128-bit integers.strings strings library contains a variety of strings routines and utilities, including a C++11-compatible version of the C++17 std::string_view type.synchronization synchronization library contains concurrency primitives (Abseil's absl::Mutex class, an alternative to std::mutex) and a variety of synchronization abstractions.time time library contains abstractions for computing with absolute points in time, durations of time, and formatting and parsing time within time zones.types types library contains non-container utility types, like a C++11-compatible version of the C++17 std::optional type.utility utility library contains utility and helper code.The Abseil C++ library is licensed under the terms of the Apache license. See LICENSE for more information.
For more information about Abseil: