| commit | fff745773f54db0fcbda956f9ed5658c751cf9a2 | [log] [tgz] |
|---|---|---|
| author | Amirali Abdolrashidi <abdolrashidi@google.com> | Thu Jan 25 01:15:01 2024 |
| committer | Copybara-Service <copybara-worker@google.com> | Thu Jan 25 01:24:09 2024 |
| tree | fe86f4e3be3c9e12ef6d78fd19abc84f3bc35ad9 | |
| parent | cc7458fad1e5fa2ee2bcc8e92af90aef952087e5 [diff] |
Drop support for VMA 2.0 in Chromium Following the change in ANGLE to remove support for VMA 2.0, we can now remove this support for Chromium as well. * ANGLE change to drop VMA 2.0: https://crrev.com/c/4791667 * Removed angle_vma_version from angle.gni, since it is no longer required. Cq-Include-Trybots: luci.chromium.try:linux_chromium_msan_rel_ng Bug: b/303290680 Change-Id: I075386f8cabda7deee39288bb5175e38f45fb80a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5186752 Commit-Queue: Amirali Abdolrashidi <abdolrashidi@google.com> Reviewed-by: Peng Huang <penghuang@chromium.org> Reviewed-by: Thomas Anderson <thomasanderson@chromium.org> Cr-Commit-Position: refs/heads/main@{#1251840} NOKEYCHECK=True GitOrigin-RevId: c7cfd733b7b53eb0c17646dd18810d38d9055496
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.