Remove overrides needed for Meson based Mesa build Now that https://dawn-review.googlesource.com/c/dawn/+/352795 has landed and rolled into Chromium these values are no longer be needed. Bug: 576167708 Change-Id: I7d73ab8f0ed14c31751a229269839875c8a14d8d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/8625348 Auto-Submit: Ryan Harrison <rharrison@chromium.org> Commit-Queue: Andrew Grieve <agrieve@chromium.org> Reviewed-by: dan sinclair <dsinclair@chromium.org> Reviewed-by: Andrew Grieve <agrieve@chromium.org> Cr-Commit-Position: refs/heads/main@{#1727145} NOKEYCHECK=True GitOrigin-RevId: 018a1e63c2ee42dde74fbca8c90b48579cb4f014
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/41240413): 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.