commit | fed6fcd9f15c04e39cb9bccf396b80be2de32a10 | [log] [tgz] |
---|---|---|
author | Peter Wen <wnwen@chromium.org> | Thu Jul 11 20:57:23 2024 |
committer | Copybara-Service <copybara-worker@google.com> | Thu Jul 11 21:00:37 2024 |
tree | b8c693b104a3dcfa53c649843b41847a9314884e | |
parent | 6f9209191fc2fa083c4d8aa78262053057d85b54 [diff] |
lorenz: Switch to using gn_helpers Hopefully this coupled with a build cache clean will be able to resolve the issue on the lorenz bot. Bug: 348423879 Change-Id: I840ab9c638c0cd1056528ab0ab2a26835f83371a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5698025 Auto-Submit: Peter Wen <wnwen@chromium.org> Commit-Queue: Henrique Nakashima <hnakashima@chromium.org> Reviewed-by: Henrique Nakashima <hnakashima@chromium.org> Cr-Commit-Position: refs/heads/main@{#1326380} NOKEYCHECK=True GitOrigin-RevId: 29b80e84a08adb3ea61c01ab15d7e616997cef5e
//build
contains:
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.
//build/config
- Common templates via .gni
files.//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 all BUILD.gn
files.//build/secondary
- An overlay for BUILD.gn
files. Enables adding BUILD.gn
to directories that live in sub-repositories.//build_overrides
- Refer to //build_overrides/README.md.