1 # This file is used by the GN meta build system to find the root of the source
2 # tree and to set startup options. For documentation on the values set in this
3 # file, run "gn help dotfile" at the command line.
5 import("//build/dotfile_settings.gni")
6 import("//third_party/angle/dotfile_settings.gni")
8 # The location of the build configuration file.
9 buildconfig = "//build/config/BUILDCONFIG.gn"
11 # The python interpreter to use by default. On Windows, this will look
12 # for python3.exe and python3.bat.
13 script_executable = "python3"
15 # These arguments override the default values for items in a declare_args
16 # block. "gn args" in turn can override these.
18 # In general the value for a build arg in the declare_args block should be the
19 # default. In some cases, a DEPS-ed in project will want different defaults for
20 # being built as part of Chrome vs. being built standalone. In this case, the
21 # Chrome defaults should go here. There should be no overrides here for
22 # values declared in the main Chrome repository.
24 # Important note for defining defaults: This file is executed before the
25 # BUILDCONFIG.gn file. That file sets up the global variables like "is_ios".
26 # This means that the default_args can not depend on the platform,
27 # architecture, or other build parameters. If you really need that, the other
28 # repo should define a flag that toggles on a behavior that implements the
29 # additional logic required by Chrome to set the variables.
31 # TODO(brettw) bug 684096: Chrome on iOS does not build v8, so "gn gen" prints
32 # a warning that "Build argument has no effect". When adding a v8 variable, it
33 # also needs to be defined to src/ios/BUILD.gn (respectively removed from both
34 # location when it is removed).
36 v8_enable_gdbjit = false
37 v8_imminent_deprecation_warnings = false
39 # Don't include webrtc's builtin task queue implementation.
40 rtc_link_task_queue_impl = false
42 # When building with Chromium, `webrtc::Location` is replaced by
43 # `base::Location`. Since WebRTC doesn't use `public_deps` (webrtc:8603), it
44 # would fail to propagate the dependency internally. Instead WebRTC let its
45 # embedders to define it globally for all of its targets.
46 rtc_common_public_deps = [ "//base" ]
48 # Don't include the iLBC audio codec.
49 # TODO(bugs.webrtc.org/8396): Once WebRTC gets rid of its internal
50 # deps on codecs, we can remove this.
51 rtc_include_ilbc = false
53 # Changes some setup for the Crashpad build to set them to build against
54 # Chromium's zlib, base, etc.
55 crashpad_dependencies = "chromium"
57 # Override ANGLE's Vulkan dependencies.
58 angle_vulkan_headers_dir = "//third_party/vulkan-deps/vulkan-headers/src"
59 angle_vulkan_loader_dir = "//third_party/vulkan-deps/vulkan-loader/src"
60 angle_vulkan_tools_dir = "//third_party/vulkan-deps/vulkan-tools/src"
61 angle_vulkan_validation_layers_dir =
62 "//third_party/vulkan-deps/vulkan-validation-layers/src"
64 # Overwrite default args declared in the Fuchsia sdk
65 fuchsia_sdk_readelf_exec =
66 "//third_party/llvm-build/Release+Asserts/bin/llvm-readelf"
68 # Overwrite default args declared in the pdfium library
69 pdf_use_partition_alloc_new_location = true
71 devtools_visibility = [ "*" ]
74 # These are the targets to skip header checking by default. The files in targets
75 # matching these patterns (see "gn help label_pattern" for format) will not have
76 # their includes checked for proper dependencies when you run either
77 # "gn check" or "gn gen --check".
79 # //v8, https://crbug.com/v8/7330
80 "//v8/src/inspector:inspector", # 20 errors
81 "//v8/test/cctest:cctest_sources", # 15 errors
82 "//v8/test/unittests:inspector_unittests_sources", # 2 errors
83 "//v8:cppgc_base", # 1 error
84 "//v8:v8_internal_headers", # 11 errors
85 "//v8:v8_libplatform", # 2 errors
88 # These are the list of GN files that run exec_script. This whitelist exists
89 # to force additional review for new uses of exec_script, which is strongly
94 # You should almost never need to add new exec_script calls. exec_script is
95 # slow, especially on Windows, and can cause confusing effects. Although
96 # individually each call isn't slow or necessarily very confusing, at the scale
97 # of our repo things get out of hand quickly. By strongly pushing back on all
98 # additions, we keep the build fast and clean. If you think you need to add a
99 # new call, please consider:
101 # - Do not use a script to check for the existence of a file or directory to
102 # enable a different mode. Instead, use GN build args to enable or disable
103 # functionality and set options. An example is checking for a file in the
104 # src-internal repo to see if the corresponding src-internal feature should
105 # be enabled. There are several things that can go wrong with this:
107 # - It's mysterious what causes some things to happen. Although in many cases
108 # such behavior can be conveniently automatic, GN optimizes for explicit
109 # and obvious behavior so people can more easily diagnose problems.
111 # - The user can't enable a mode for one build and not another. With GN build
112 # args, the user can choose the exact configuration of multiple builds
113 # using one checkout. But implicitly basing flags on the state of the
114 # checkout, this functionality is broken.
116 # - It's easy to get stale files. If for example the user edits the gclient
117 # to stop checking out src-internal (or any other optional thing), it's
118 # easy to end up with stale files still mysteriously triggering build
119 # conditions that are no longer appropriate (yes, this happens in real
122 # - Do not use a script to iterate files in a directory (glob):
124 # - This has the same "stale file" problem as the above discussion. Various
125 # operations can leave untracked files in the source tree which can cause
126 # surprising effects.
128 # - It becomes impossible to use "git grep" to find where a certain file is
129 # referenced. This operation is very common and people really do get
130 # confused when things aren't listed.
132 # - It's easy to screw up. One common case is a build-time script that packs
133 # up a directory. The author notices that the script isn't re-run when the
134 # directory is updated, so adds a glob so all the files are listed as
135 # inputs. This seems to work great... until a file is deleted. When a
136 # file is deleted, all the inputs the glob lists will still be up to date
137 # and no command-lines will have been changed. The action will not be
138 # re-run and the build will be broken. It is possible to get this correct
139 # using glob, and it's possible to mess it up without glob, but globs make
140 # this situation much easier to create. if the build always lists the
141 # files and passes them to a script, it will always be correct.
143 exec_script_whitelist =
144 build_dotfile_settings.exec_script_whitelist +
145 angle_dotfile_settings.exec_script_whitelist +
147 # Whitelist entries for //build should go into
148 # //build/dotfile_settings.gni instead, so that they can be shared
149 # with other repos. The entries in this list should be only for files
150 # in the Chromium repo outside of //build.
151 "//build_overrides/build.gni",
153 "//chrome/android/webapk/shell_apk/prepare_upload_dir/BUILD.gn",
154 "//chrome/version.gni",
156 # TODO(dgn): Layer violation but breaks the build otherwise, see
157 # https://crbug.com/474506.
158 "//clank/java/BUILD.gn",
159 "//clank/native/BUILD.gn",
161 "//google_apis/BUILD.gn",
162 "//printing/BUILD.gn",
164 "//remoting/host/installer/linux/BUILD.gn",
165 "//remoting/remoting_version.gni",
166 "//remoting/host/installer/win/generate_clsids.gni",
168 "//tools/grit/grit_rule.gni",
169 "//tools/gritsettings/BUILD.gn",