| commit | da70fd0b84bc491976c4ce808102acb847fbc4e0 | [log] [tgz] |
|---|---|---|
| author | Colin Cross <ccross@android.com> | Mon Dec 30 18:40:09 2019 -0800 |
| committer | Colin Cross <ccross@android.com> | Thu Jan 02 20:32:51 2020 -0800 |
| tree | 4db72c3821d6dbfad46d591333ad285c3b19158e | |
| parent | 9999eddc4687d0dedd0cf36abeff605781e69b3c [diff] |
Move LoadHooks from Soong to Blueprint Move LoadHooks from Blueprint and run them during ParseBlueprintsFiles. This will allow them to add scoped module types that are visible to the rest of the Blueprints file. Requires passing the config object to ParseBlueprintsFiles. Test: all blueprint tests Change-Id: Ia2a2c9a0223d5458bfd48bd22ebed0fdbd0156c6
- bootstrap/command.go[diff]
- context.go[diff]
- context_test.go[diff]
- module_ctx.go[diff]
- module_ctx_test.go[diff]
- visit_test.go[diff]
6 files changed
tree: 4db72c3821d6dbfad46d591333ad285c3b19158e
- bootstrap/
- bpfmt/
- bpmodify/
- deptools/
- gotestmain/
- gotestrunner/
- loadplugins/
- microfactory/
- parser/
- pathtools/
- proptools/
- tests/
- .gitignore
- .travis.fix-fork.sh
- .travis.gofmt.sh
- .travis.install-ninja.sh
- .travis.yml
- 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
- unpack.go
- unpack_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.