Assert when using FORCE_MAC_TOOLCHAIN and target_os=ios.

iOS no longer uses the hermetic Xcode toolchain.

Bug: 939785
Change-Id: I31a28e77a7e2b5b43f3db43c39ada9d9e6757540
Reviewed-by: Nico Weber <>
Reviewed-by: Erik Chen <>
Auto-Submit: Justin Cohen <>
Commit-Queue: Justin Cohen <>
Cr-Original-Commit-Position: refs/heads/master@{#644418}
Cr-Mirrored-Commit: 4b820a46fc4a38a597c72851e322b1be4aa7984b
1 file changed
tree: 31bc936341b51062d68cf54ca3ca883fba6a920c
  3. angle.gni
  4. build.gni
  5. dawn.gni
  6. glslang.gni
  7. gtest.gni
  8. pdfium.gni
  9. shaderc.gni
  10. spirv_tools.gni

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