| commit | dad7f351731a2925f5d02fef239a101a7332d1f0 | [log] [tgz] |
|---|---|---|
| author | dpranke <dpranke@chromium.org> | Thu Oct 29 00:48:15 2015 |
| committer | Commit bot <commit-bot@chromium.org> | Thu Oct 29 00:49:52 2015 |
| tree | 77587299ea804df8953169bf1ed63602c38569be | |
| parent | a623ab9abd74a70d93ddb8b015fc6656f9e7d0f2 [diff] |
Add an OWNERS file to //build_overrides. R=brettw@chromium.org, jam@chromium.org BUG= Review URL: https://codereview.chromium.org/1416873013 Cr-Original-Commit-Position: refs/heads/master@{#356707} Cr-Mirrored-From: https://chromium.googlesource.com/chromium/src Cr-Mirrored-Commit: d69d969f2f857400d74a2699dd9b33b30b5e4496
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.