gn, mac: Various GN build fixes

- Don't pass unrecognized flags to linker
- Set -fno-exceptions (matching gyp)
- Add .S handling for capture_context.S (assembling via clang++)
- Don't prefix .so with "lib"

Not sure if this is complete yet, but with this, I get this same output

[==========] Running 44 tests from 11 test cases.
[==========] Running 1 test from 1 test case.
[==========] Running 113 tests from 25 test cases.
[==========] Running 45 tests from 12 test cases.
[==========] Running 19 tests from 8 test cases.
[==========] Running 386 tests from 77 test cases.

from Mac gn and Mac gyp.

Bug: crashpad:79
Change-Id: Iec244fe5ee808bee49569cbba2ed6b16959531d1
Reviewed-on: https://chromium-review.googlesource.com/818492
Reviewed-by: Mark Mentovai <mark@chromium.org>
1 file changed
tree: 0726abe7ed0f947242ee162b629ccd986402e78b
  1. base/
  2. build/
  3. .gitignore
  4. AUTHORS
  5. BUILD.gn
  6. codereview.settings
  7. LICENSE
  8. mini_chromium.gyp
  9. README.md
README.md

mini_chromium

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