[fuchsia] Enable backup-ref-ptr under Fuchsia

Enable backup-ref-ptr in the build, to allow checks to be applied in
the browser process of the WebEngine.

This requires a small teardown ordering fix in the CastStreamingSession.

Fuchsia-Binary-Size: Unavoidable due to raw_ptr/ref instrumentation.
Bug: 345766776, 346197731
Change-Id: Ia9597d9ccf568d4812d82a5e2a01f112debec2e0
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5401762
Auto-Submit: Wez <wez@chromium.org>
Reviewed-by: Kentaro Hara <haraken@chromium.org>
Commit-Queue: Wez <wez@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1313945}
NOKEYCHECK=True
GitOrigin-RevId: 7cb29b1cc84e6dbf699611a50ac9989b3a7d1c53
1 file changed
tree: 573057a8efd6c178091cc24889d03547e8b3426c
  1. angle.gni
  2. build.gni
  3. dawn.gni
  4. glslang.gni
  5. gtest.gni
  6. ipcz.gni
  7. OWNERS
  8. partition_alloc.gni
  9. pdfium.gni
  10. README.md
  11. spirv_tools.gni
  12. swiftshader.gni
  13. tint.gni
  14. vulkan_common.gni
  15. vulkan_headers.gni
  16. vulkan_loader.gni
  17. vulkan_tools.gni
  18. vulkan_utility_libraries.gni
  19. vulkan_validation_layers.gni
  20. wayland.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/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.