Use Dawn's copy of GLFW since it manages its build file.

This is to:
 - Add Wayland support to Dawn's swapchains, which requires to
 - Upgrade GLFW to detect X11 vs. Wayland in testing, which requires to
 - Roll GLFW to a version that supports Wayland, which requires to
 - Update GLFW's BUILD.gn file that live in Dawn's repo.

Bug: dawn:1246
Change-Id: I7cf80ea27756a46f2db495ece26733b57be81541
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3663229
Reviewed-by: Sylvain Defresne <sdefresne@chromium.org>
Auto-Submit: Corentin Wallez <cwallez@chromium.org>
Commit-Queue: Sylvain Defresne <sdefresne@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1007358}
NOKEYCHECK=True
GitOrigin-RevId: bf79bbd8e50d9c55539af88253b26aaaaad5fcd8
1 file changed
tree: 3751a0de80d7ef84e87b29fcfe65de668bc308ae
  1. angle.gni
  2. build.gni
  3. dawn.gni
  4. glslang.gni
  5. gtest.gni
  6. ipcz.gni
  7. OWNERS
  8. pdfium.gni
  9. README.md
  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
README.md

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