| commit | 404f6dbf9928dd19cb437ad5b05abfdd97b5bf67 | [log] [tgz] |
|---|---|---|
| author | Mark Mentovai <mark@chromium.org> | Tue Dec 19 14:18:49 2017 -0500 |
| committer | Mark Mentovai <mark@chromium.org> | Tue Dec 19 19:18:57 2017 +0000 |
| tree | f08b0e7c015505fc76c7683e77a9bdc1e54f3429 | |
| parent | c913ef97a23624c83896f45e027e319389fed3a9 [diff] |
gn: Don’t use .rsp files; rationalize descriptions and output dirs .rsp files were omitted from the Windows build (where they’re probably more likely to be useful) for simplicity, since mini_chromium and Crashpad shouldn’t need them. They were left in place for link steps on other platforms, though. This removes the use of .rsp files, which should make it easier to debug the build. Some of the tool descriptions were a little wacky. Some were just plain wrong, and others were just a little wrong. Rather than trying to match Chromium step-for-step, this standardizes on a set of meaningful and recognizable names not likely to be confused for anything else: CC, CXX, OBJC, OBJCXX, ASM, AR, SOLINK_MODULE, LINK, STAMP, and COPY. Output directories are also handled more consistently. The Objective-C steps are defined on macOS only. Bug: crashpad:79 Change-Id: I1160279f06ccbb663087be494795588f4a637843 Reviewed-on: https://chromium-review.googlesource.com/834228 Reviewed-by: Scott Graham <scottmg@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