19d16a4bc9
If you look at these two patchsets the only difference is this change https://crrev.com/c/3089797/16 https://crrev.com/c/3089797/17 However 17 fails without it due to a timeout Bug: 1241651 Change-Id: I95b27b8fe4831e170ee7c9f5ae22435b2425c885 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3111092 Commit-Queue: Struan Shrimpton <sshrimp@google.com> Reviewed-by: Gregory Guterman <guterman@google.com> Reviewed-by: Dirk Pranke <dpranke@google.com> Cr-Commit-Position: refs/heads/main@{#914856}
About
//build contains:
- Core GN templates and configuration
- Core Python build scripts
Since this directory is DEPS'ed in by some other repositories (webrtc, pdfium,
v8, etc), it should be kept as self-contained as possible by not referring
to files outside of it. Some exceptions exist (//testing, select
//third_party subdirectories), but new dependencies tend to break these other
projects, and so should be avoided.
Changes to //build should be landed in the Chromium repo. They will then be
replicated to the stand-alone build repo
by the gsubtreed tool.
Note: You can find all directories already available through gsubtreed in the
list of all chromium repos.
Contents
//build/config- Common templates via.gnifiles.//build/toolchain- GN toolchain definitions.Other .py files- Some are used by GN/Ninja. Some by gclient hooks, some are just random utilities.
Files referenced by //.gn:
//build/BUILDCONFIG.gn- Included by allBUILD.gnfiles.//build/secondary- An overlay forBUILD.gnfiles. Enables addingBUILD.gnto directories that live in sub-repositories.//build_overrides- Refer to //build_overrides/README.md.