commit | 199de5ff0d22c2c220ce342192d61f2e465ead04 | [log] [tgz] |
---|---|---|
author | Maksim Sisov <msisov@igalia.com> | Thu Oct 06 08:49:02 2022 |
committer | Copybara-Service <copybara-worker@google.com> | Thu Oct 06 08:59:49 2022 |
tree | af27fa0359f1737814556f502c7730235ec6078e | |
parent | 28f4beac31c8c9cc77267f691d15f479d7bd70a5 [diff] |
wayland: automatically generate all required headers/sources client-header/server-header and public-code are now automatically generated using wayland_protocol template that understands what kind of config it needs. This will simplify future upgrades of libwayland. Tested with use_system_libwayland_server and use_system_libwayland_client set to {{false, false},{true,false},{true,true},{false,true}}. Bug: 1371438 Change-Id: I9aa722f141a76f7a4a660b9b44447993e3e37459 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3913335 Reviewed-by: Mitsuru Oshima <oshima@chromium.org> Reviewed-by: Thomas Anderson <thomasanderson@chromium.org> Commit-Queue: Maksim Sisov <msisov@igalia.com> Cr-Commit-Position: refs/heads/main@{#1055667} NOKEYCHECK=True GitOrigin-RevId: d2ed9657e98d4330d01f133a398f0bee39067181
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.