| commit | 607e9cf098a57d50a25fc3ce3a1b8d9da0f94b35 | [log] [tgz] |
|---|---|---|
| author | erikchen <erikchen@chromium.org> | Fri Oct 21 17:10:27 2016 |
| committer | Commit bot <commit-bot@chromium.org> | Fri Oct 21 17:13:40 2016 |
| tree | 0f0d1ad169169284d8b6283bc355c9604818aca5 | |
| parent | 57e7d01464c97814eddb8a5c038352b833c2ad90 [diff] |
Bump Chrome's deployment target to macOS 10.8. I also updated the comment to better reflect the relationship between Chrome and its dependencies. Several Chrome dependencies require a different min sdk and/or deployment target from Chrome. BUG=622481 Committed: https://crrev.com/3dade40fe88881864a42134f92238a6d292d8505 Review-Url: https://chromiumcodereview.appspot.com/2420233002 Cr-Original-Commit-Position: refs/heads/master@{#426822} Cr-Original-Original-Commit-Position: refs/heads/master@{#425870} Cr-Mirrored-From: https://chromium.googlesource.com/chromium/src Cr-Mirrored-Commit: 45fd5f3efc52919eea92025f2ae95ba244bff176
This directory is used to allow different products to customize settings for repos that are DEPS'ed in or shared.
For example: V8 could be built on its own (in a “standalone” configuration), and it could be built as part of Chromium. V8 might define a top-level target, //v8:d8 (a simple executable), that should only be built in the standalone configuration. To figure out whether or not it should be in a standalone configuration, v8 can create a file, build_overrides/v8.gni, that contains a variable, build_standalone_d8 = true. and import it (as import(“//build_overrides/v8.gni”) from its top-level BUILD.gn file.
Chromium, on the other hand, might not need to build d8, and so it would create its own build_overrides/v8.gni file, and in it set build_standalone_d8 = false.
The two files should define the same set of variables, but the values can vary as appropriate to the needs of the two different builds.
The build.gni file provides a way for projects to override defaults for variables used in //build itself (which we want to be shareable between projects).
TODO(crbug.com/588513): Ideally //build_overrides and, in particular, //build_overrides/build.gni should go away completely in favor of some mechanism that can re-use other required files like //.gn, so that we don't have to keep requiring projects to create a bunch of different files to use GN.