commit | 1a5a3d0df60d8bc59f27f124cc1c182a643bf1d7 | [log] [tgz] |
---|---|---|
author | Milad Fa <[email protected]> | Fri Feb 07 17:01:28 2025 |
committer | Copybara-Service <[email protected]> | Fri Feb 07 17:03:59 2025 |
tree | fa450e9f30304a9717c6803bb4b3a28cbbebccfb | |
parent | 74f6e21c55b0f63b730422e889d7b616002e3f69 [diff] |
Fix compilation with gcc Bug: 40440396 Change-Id: I12f600e9b0f5ef86c78ca11cb2ceed98e8e12458 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6237827 Reviewed-by: Nico Weber <[email protected]> Reviewed-by: Hans Wennborg <[email protected]> Commit-Queue: Nico Weber <[email protected]> Cr-Commit-Position: refs/heads/main@{#1417382} NOKEYCHECK=True GitOrigin-RevId: dd08a0dd52e4239b53b45383b052a2bac44814c6
//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.