GN: Wayland build overrides

Introduce //build_overrides/wayland.gni to simplify the management of
the wayland dependencies in Chromium, ANGLE, and SwiftShader.

Bug: 1327041, angleproject:7409
Change-Id: Ia178f09303c772a5cce5f9c6b93a4ef2a9381102
Reviewed-by: Nico Weber <>
Reviewed-by: Peng Huang <>
Reviewed-by: Corentin Wallez <>
Commit-Queue: Yuly Novikov <>
Cr-Commit-Position: refs/heads/main@{#1013661}
GitOrigin-RevId: 3d415c7d0eba78f0b18e2c1fe1e84e4afa7e66e2
3 files changed
tree: 880d021dfc00de64692585386570aae36dd7d969
  1. angle.gni
  2. build.gni
  3. dawn.gni
  4. glslang.gni
  5. gtest.gni
  6. ipcz.gni
  8. pdfium.gni
  10. spirv_tools.gni
  11. swiftshader.gni
  12. tint.gni
  13. vulkan_common.gni
  14. vulkan_headers.gni
  15. vulkan_loader.gni
  16. vulkan_tools.gni
  17. vulkan_validation_layers.gni
  18. wayland.gni

Build overrides in GN

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 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( 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.