commit | 70b7352a6407da5085e1a7b49ac8f4e885b1faf5 | [log] [tgz] |
---|---|---|
author | Andrew Grieve <[email protected]> | Mon Jan 20 17:17:00 2025 |
committer | Copybara-Service <[email protected]> | Mon Jan 20 17:45:21 2025 |
tree | 4738908f8fad4406b685bd828c11c037655695e4 | |
parent | 64e296c42a93fbd27acc9a94713e4289273409b2 [diff] |
private_code_test: Parse build.ninja to collect linker inputs Although slower, this handles the case where GN targets are in public code, but include source files from private code. Bug: 40204298 Change-Id: If571518f07855946a16e5aeebe0cace661cc75dd Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5756917 Commit-Queue: Andrew Grieve <[email protected]> Reviewed-by: Dirk Pranke <[email protected]> Cr-Commit-Position: refs/heads/main@{#1408713} NOKEYCHECK=True GitOrigin-RevId: a6dddc3de16b5c67656254e10ed648354cd3a4f0
//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.