| commit | 9b45df850a4f717bdc1e040e669fbaebe167c65f | [log] [tgz] |
|---|---|---|
| author | Kai Ninomiya <kainino@chromium.org> | Thu Aug 31 00:05:21 2023 |
| committer | Copybara-Service <copybara-worker@google.com> | Thu Aug 31 00:14:45 2023 |
| tree | 443516aa2c721f404c57db2ac8e617cc7066971c | |
| parent | 2be34a9680f7999b692b0dad99918447516b228b [diff] |
Add build overrides for Vulkan Utility Libraries This is a new dependency for Vulkan-ValidationLayers Bug: angleproject:8318 Change-Id: I0981115fea99effaa1d8f19af1a56a627d4d8cef Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4828632 Reviewed-by: Thomas Anderson <thomasanderson@chromium.org> Commit-Queue: Kai Ninomiya <kainino@chromium.org> Auto-Submit: Kai Ninomiya <kainino@chromium.org> Commit-Queue: Thomas Anderson <thomasanderson@chromium.org> Cr-Commit-Position: refs/heads/main@{#1190425} NOKEYCHECK=True GitOrigin-RevId: ce0a8999547990461e9cc1448f921c9cededac34
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.