commit | ab6d790165d557a2764f76f6dff6bfba57450310 | [log] [tgz] |
---|---|---|
author | Colin Cross <ccross@android.com> | Wed Mar 11 16:17:52 2015 -0700 |
committer | Colin Cross <ccross@android.com> | Thu Mar 12 17:36:57 2015 -0700 |
tree | 173d0d0d2d66370240ca39bde1307b6ba6b840bc | |
parent | 7addea35a1e29c53843db684252cd73c1a911c9b [diff] |
Move build actions into modules Move actionDefs from moduleGroup to moduleInfo. This will result in multiple build.ninja headers for a single Blueprint file module if it has multiple variants, each one specifying the variant used to generate the following rules. Change-Id: I414cd4d3266da8c2e92118b295569627ddf48cdd
Blueprint is a meta-build system that reads in Blueprints files that describe modules that need to be built, and produces a Ninja (http://martine.github.io/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 langauge 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.