| commit | 2da8492b9da69c54bb52cd7de9486e0985c7e984 | [log] [tgz] |
|---|---|---|
| author | Colin Cross <ccross@android.com> | Thu Jul 02 10:08:12 2020 -0700 |
| committer | Colin Cross <ccross@android.com> | Tue Sep 22 18:20:18 2020 -0700 |
| tree | df1585f8e87ff8607c0ee6f19b326cacf74242fd | |
| parent | 66fa73dd6e22839346531e341b2ca80726ab0979 [diff] |
Add Providers to Blueprint Providers are a new concept for Blueprint, based on providers in Bazel: https://docs.bazel.build/versions/master/skylark/rules.html#providers Providers aim to simplify the interaction between modules by replacing type asserting to arbitrary interfaces with requesting optional data objects from modules. This will also move Blueprint closer to supporting incremental analysis by serializing the providers and only rerunning the analysis phase on modules whose inputs have changed. Change-Id: I39f5f78b372412a7dbf151ceccb3f917f6c874bf
- Blueprints[diff]
- context.go[diff]
- module_ctx.go[diff]
- provider.go[Added - diff]
- provider_test.go[Added - diff]
- singleton_ctx.go[diff]
6 files changed
tree: df1585f8e87ff8607c0ee6f19b326cacf74242fd
- .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
- provider.go
- provider_test.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.