linux: Switch between x86 and x86_64 with the target_arch GYP variable When targeting Linux on x86, with proper toolchain support, it’s possible to switch the target in a native (non-cross) build by using -m32 and -m64. Use the GYP target_arch variable to direct this, as was done for Mac in 6c49a5924dea. This is only done for OS=="linux", and notably not OS=="android", which must always be configured as a cross build. Bug: crashpad:30 Change-Id: I4a0b0d0ffd9911a18c155fa9a991ccd31ce08d25 Reviewed-on: https://chromium-review.googlesource.com/553319 Reviewed-by: Robert Sesek <rsesek@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