commit | e443d638d57c28893f852895caa8b5dd8c97b77b | [log] [tgz] |
---|---|---|
author | Antonio Caggiano <antonio.caggiano@collabora.com> | Wed Apr 06 16:46:27 2022 |
committer | Copybara-Service <copybara-worker@google.com> | Wed Apr 06 16:57:10 2022 |
tree | 4774f66a31fa1a5dcff7b645d5bf29e76d5c9ed3 | |
parent | f3f03a8bf07df428116319b0ed5c88ca2c00ef99 [diff] |
Wayland: Add Vulkan definitions Use ozone_platform_wayland to set vulkan_use_wayland. This is then used by Vulkan dependencies BUILD.gn to add any Wayland definitions such as VK_USE_PLATFORM_WAYLAND_KHR. Bug: 1291937 Change-Id: I0494d030c486d08af89d5698dda8b1acefd19699 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3455146 Reviewed-by: Mirko Bonadei <mbonadei@chromium.org> Reviewed-by: Nico Weber <thakis@chromium.org> Reviewed-by: Peng Huang <penghuang@chromium.org> Auto-Submit: Antonio Caggiano <antonio.caggiano@collabora.com> Reviewed-by: Jamie Madill <jmadill@chromium.org> Commit-Queue: Jamie Madill <jmadill@chromium.org> Cr-Commit-Position: refs/heads/main@{#989472} NOKEYCHECK=True GitOrigin-RevId: cb982fd0868ab3a3d4274a997568d9120c4b2d66
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.