| commit | d70bf75491b5b234eccb77d0a1e841a8391ebe07 | [log] [tgz] |
|---|---|---|
| author | Jeff Gaston <jeffrygaston@google.com> | Fri Nov 10 15:12:08 2017 -0800 |
| committer | Jeff Gaston <jeffrygaston@google.com> | Wed Nov 29 12:01:09 2017 -0800 |
| tree | ee7f78837f297dcbf348d4edb390537a9345d53d | |
| parent | 90d258833aaee2c53a7f7fe6fd549c8a992dc7ee [diff] |
Extract module naming into an interface
in facilitate moving name resolution to Soong
Bug: 65683273
Test: build/soong/scripts/diff_build_graphs.sh \
--products=aosp_arm \
'build/blueprint:work^' 'build/blueprint:work'
# and see that the only changes were:
# 1. adding the name_interface.go file
# 2. changing some line numbers
Change-Id: Ifa7603cca59b3b3d592f2f146fdafe57012bd4b9
- Blueprints[diff]
- context.go[diff]
- context_test.go[diff]
- module_ctx.go[diff]
- name_interface.go[Added - diff]
- visit_test.go[diff]
6 files changed
tree: ee7f78837f297dcbf348d4edb390537a9345d53d
- 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
- LICENSE
- live_tracker.go
- mangle.go
- module_ctx.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.