| commit | e182031c61072f629494a1f52729a8d29a6acace | [log] [tgz] |
|---|---|---|
| author | Scott Graham <scottmg@chromium.org> | Mon Dec 18 15:55:50 2017 -0800 |
| committer | Scott Graham <scottmg@chromium.org> | Mon Dec 18 23:56:08 2017 +0000 |
| tree | afc75bf471cb2601438759e56c5bff1ac99fb338 | |
| parent | 4cb13447b1e516f04f855679a48b7696312d7eb8 [diff] |
gn: Add is_posix.gni to define local is_posix variable The in-Fuchsia build doesn't have an is_posix in BUILDCONFIG.gn, so create one here for use by mini_chromium and Crashpad. I've also been thinking about potentially not following Chromium here, and using only real Zircon, rather than fake POSIX too, so mini_chromium having its own might facilitate that in the future, as we'd likely want to have is_posix be false in that case. Bug: crashpad:79, crashpad:196 Change-Id: Ifca6ddc678eb25755ec98e7b1bec24e304130ec4 Reviewed-on: https://chromium-review.googlesource.com/833328 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