commit | ac45bd1ea824a274d9347f3d01671d959065ac15 | [log] [tgz] |
---|---|---|
author | Colin Cross <ccross@android.com> | Wed Sep 20 14:09:52 2017 -0700 |
committer | Colin Cross <ccross@android.com> | Wed Sep 20 14:09:52 2017 -0700 |
tree | d6365d153fb5abc15a3e1c647dd358fc05c87208 | |
parent | e8abb6038e658de3f24dc236d9bcca1dd06a937e [diff] | |
parent | b67c1d433cf9359a4fb5e30babfa7df10c965bf0 [diff] |
Merge remote-tracking branch 'aosp/upstream' into master * aosp/upstream: travis: run short tests with race detector enabled Let mutators use ctx.AddNinjaFileDeps Add TopDownMutatorContext.CreateModule Replace unpack's replace semantics with append Rename newModules to newVariations Rename moduleInfo.moduleProperties to properties Test: m -j checkbuild Change-Id: I95eaeabbac307124fdc42249f315ad8e172ca029
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.