| commit | 55252655d26f96278fffff4f270ff804822f8b0b | [log] [tgz] |
|---|---|---|
| author | Dan Willemsen <dwillemsen@google.com> | Wed Jun 24 13:30:26 2020 -0700 |
| committer | Dan Willemsen <dwillemsen@google.com> | Wed Jun 24 14:23:22 2020 -0700 |
| tree | 31c5d23fd6954b0b1b56b734066bb7571eec3907 | |
| parent | 2c0cd0ac8ded67ef06a247799187dad58b8ae5cd [diff] |
Stop writing depfiles from Glob singleton This makes a minimal difference on my AOSP tree (which is on a fast NVME drive), but it saves ~10-15% of the time in our primary builder (soong_build) on larger trees on slower drives. We're always going to run the glob tool at least once outside of the primary builder, and ninja only loads depfiles created after running the tool, so this should be a no-op change. We still need to write the list file (if it has changed), since that's the file we're adding as a dependency of the primary builder, so the effective timestamp must be earlier than the build.ninja timestamp. Change-Id: I872b7581da50e7f2089daa7e248ca05b6703f019
1 file changed
tree: 31c5d23fd6954b0b1b56b734066bb7571eec3907
- .github/
- bootstrap/
- bpfmt/
- bpmodify/
- deptools/
- gotestmain/
- gotestrunner/
- loadplugins/
- microfactory/
- parser/
- pathtools/
- proptools/
- tests/
- .gitignore
- .gofmt.sh
- blueprint.bash
- blueprint_impl.bash
- Blueprints
- bootstrap.bash
- context.go
- context_test.go
- CONTRIBUTING.md
- doc.go
- glob.go
- glob_test.go
- go.mod
- LICENSE
- live_tracker.go
- mangle.go
- module_ctx.go
- module_ctx_test.go
- name_interface.go
- ninja_defs.go
- ninja_strings.go
- ninja_strings_test.go
- ninja_writer.go
- ninja_writer_test.go
- package_ctx.go
- README.md
- scope.go
- singleton_ctx.go
- splice_modules_test.go
- visit_test.go
README.md
Blueprint Build System
Blueprint is a meta-build system that reads in Blueprints files that describe modules that need to be built, and produces a Ninja manifest describing the commands that need to be run and their dependencies. Where most build systems use built-in rules or a domain-specific language to describe the logic for converting module descriptions to build rules, Blueprint delegates this to per-project build logic written in Go. For large, heterogenous projects this allows the inherent complexity of the build logic to be maintained in a high-level language, while still allowing simple changes to individual modules by modifying easy to understand Blueprints files.