| commit | a4371358766ec8f356d09e36984c69572ad48515 | [log] [tgz] |
|---|---|---|
| author | Colin Cross <ccross@android.com> | Mon Aug 08 17:24:03 2016 -0700 |
| committer | Colin Cross <ccross@android.com> | Mon Aug 08 17:35:29 2016 -0700 |
| tree | 79002bf23ddc9e0d2a00825805d04d554a581ef8 | |
| parent | fd1ef9ec7adf31093c2859f4ec6bafbde5ba041d [diff] |
Only instantiate nil struct pointers that are used unpackProperties was instantiating all nil struct pointers in any struct that had a property set. Check if the property is set first, and only instantiate the struct if it was set. This has a slight behavioral change, as now structures that only exist through nil pointers and are never set into will not be type-checked. This should be fixed in a later patch set that moves the type checking to be done across all property structs once per factory before blueprint files are loaded. Change-Id: I0dea34d7fff76bb4fc907516a2d996e4ea2408d6
1 file changed
tree: 79002bf23ddc9e0d2a00825805d04d554a581ef8
- bootstrap/
- bpfmt/
- bpmodify/
- choosestage/
- deptools/
- gotestmain/
- gotestrunner/
- loadplugins/
- parser/
- pathtools/
- proptools/
- tests/
- .gitignore
- .travis.fix-fork.sh
- .travis.install-ninja.sh
- .travis.yml
- blueprint.bash
- Blueprints
- bootstrap.bash
- build.ninja.in
- context.go
- context_test.go
- context_test_Blueprints
- CONTRIBUTING.md
- doc.go
- LICENSE
- live_tracker.go
- mangle.go
- module_ctx.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
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.