commit | 85d56d4745828e3f9260a40b0283c4173bacd3a2 | [log] [tgz] |
---|---|---|
author | Tom Anderson <thomasanderson@chromium.org> | Thu Jun 06 17:01:31 2019 +0000 |
committer | Commit Bot <commit-bot@chromium.org> | Thu Jun 06 17:01:31 2019 +0000 |
tree | 294d85acb1efb775989cd3c2ba011dfc56afbb6a | |
parent | 5c0c876c50a74e9a790d16a8d8fb19a1350f80aa [diff] |
Fix Mac build file generation with ToT gn chrome/browser/search/BUILD.gn Full specification of the output file is needed to fix this error when gn is built with DCHECKs: [source_file.cc(21)] Check failed: !EndsWithSlash(s). //out/Release/gen/chrome/browser/search/chrome_colors/ chrome/installer/mac/BUILD.gn process_only causes process_version_rc_template to skip creating a source_set for the generated files. This is needed because the only generated file is config.py, which is invalid in a source_set. third_party/abseil-cpp/absl/debugging/BUILD.gn: New dependency is needed to fix this error with --check: ERROR at //third_party/abseil-cpp/absl/debugging/symbolize_elf.inc:70:11: Can't include this header from here. #include "absl/base/dynamic_annotations.h" ^------------------------------ The target: //third_party/abseil-cpp/absl/debugging:symbolize is including a file from the target: //third_party/abseil-cpp/absl/base:dynamic_annotations It's usually best to depend directly on the destination target. In some cases, the destination target is considered a subcomponent of an intermediate target. In this case, the intermediate target should depend publicly on the destination to forward the ability to include headers. Dependency chain (there may also be others): //third_party/abseil-cpp/absl/debugging:symbolize --> //third_party/abseil-cpp/absl/debugging:debugging_internal --[private]--> //third_party/abseil-cpp/absl/base:dynamic_annotations third_party/crashpad/crashpad/snapshot/BUILD.gn The *.proctype files are no longer allowed in static_library's. No changes in generated ninja files. BUG=964411 R=thakis Change-Id: Ibe08b8b490963caacac37a9b0cf327565a6d33b7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1641514 Reviewed-by: Nico Weber <thakis@chromium.org> Reviewed-by: Mark Mentovai <mark@chromium.org> Reviewed-by: Mirko Bonadei <mbonadei@chromium.org> Commit-Queue: Thomas Anderson <thomasanderson@chromium.org> Auto-Submit: Thomas Anderson <thomasanderson@chromium.org> Cr-Original-Commit-Position: refs/heads/master@{#666747} Cr-Mirrored-From: https://chromium.googlesource.com/chromium/src Cr-Mirrored-Commit: 9ac4b5495603235510769269d04d0cffb331ac0d
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: