| commit | 10f27f8139d692f7b6e801cf8df691a10fe46469 | [log] [tgz] |
|---|---|---|
| author | Jiyong Park <jiyong@google.com> | Fri Nov 15 18:31:56 2019 +0900 |
| committer | Jiyong Park <jiyong@google.com> | Tue Nov 19 10:45:58 2019 +0900 |
| tree | 5863c8495f72b5245b4168faed406a8d741ff809 | |
| parent | eda08050f37590ae3e5fe0da7cb1d9888f893643 [diff] |
Slice properties can be replaced override_* in Soong requires a module to override certain properties of other module. In that case, values of a slice property (e.g. []string) should be replaced by the same property value in the overriding module. However, since proptools only supports Append and Prepend orders where the original values are kept for slice properties, the behavior couldn't be implemented. To support the use case, Replace order is introduced, in which case slice property values are completely replaced. For other types of properties, the Replace order behaves exactly the same as the Append order. Bug: 144338929 Test: m Change-Id: Iae9feda035177fe6a22e6e8319c0fdaa9e08e85e
2 files changed
tree: 5863c8495f72b5245b4168faed406a8d741ff809
- 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.