| commit | 6e0fdb2e4966ec44b1ce7b8464fd7c80d1b59203 | [log] [tgz] |
|---|---|---|
| author | Scott Graham <scottmg@chromium.org> | Wed Apr 04 21:07:41 2018 |
| committer | Scott Graham <scottmg@chromium.org> | Wed Apr 04 21:48:25 2018 |
| tree | 0cf500c995911df75c15a68e87d0175c24866c84 | |
| parent | d64020797e1d5e0bcc24c1506b76320a6f7a5781 [diff] |
Repair Linux-with-sysroot build after clang update Clang switched to libc++ by default (apparently?) so force back to libstdc++ and libgcc_s when building in the limited-minspec-sysroot environment, as is done on Linux bots. Carefully selected artisinal flags from https://clang.llvm.org/docs/Toolchain.html. Bug: crashpad:30 Change-Id: I2f4251853199e5b0c6950c288aac5e2947ad5c9c Reviewed-on: https://chromium-review.googlesource.com/996452 Reviewed-by: Mark Mentovai <mark@chromium.org>
This is mini_chromium, a small collection of useful low-level (“base”) routines from the Chromium open-source project. Chromium is large, sprawling, full of dependencies, and a web browser. mini_chromium is small, self-contained, and a library. mini_chromium is especially useful as a dependency of other code that wishes to use Chromium’s base routines. By using mini_chromium, other projects’ code can function in a standalone environment outside of Chromium without having to treat all of Chromium as a dependency. When building as part of Chromium, those projects’ code can use Chromium’s own (non-mini_chromium) base implementation.
Code provided in mini_chromium provides the same interface as the equivalent code in Chromium.
While it’s a goal of mini_chromium to maintain interface compatibility with Chromium’s base library for the interfaces it does implement, there’s no requirement that it use the same implementations as Chromium’s base library. Many of the implementations used in mini_chromium are identical to Chromium’s, but many others have been modified to eliminate dependencies that are not desired in mini_chromium, and a few are completely distinct from Chromium’s altogether. Additionally, when mini_chromium provides an interface in the form of a file or class present in Chromium, it’s not bound to provide all functions, methods, or types that the Chromium equivalent does. The differences noted above notwithstanding, the interfaces exposed by mini_chromium’s base are and must remain a strict subset of Chromium’s.
Crashpad is the chief consumer of mini_chromium.
Mark Mentovai
mark@chromium.org