commit | af456eaae4a9655a6105d997eba180163849ed49 | [log] [tgz] |
---|---|---|
author | Dan Willemsen <dwillemsen@google.com> | Wed Jul 19 19:22:34 2017 -0700 |
committer | Dan Willemsen <dwillemsen@google.com> | Mon Jul 24 14:02:51 2017 -0700 |
tree | 4bc3dc281cb7f741287ae3cb1c988dc72e651cac | |
parent | f60525a63dec3cdf241756ce10a2ae4e78cc342d [diff] |
Define everything in both stages Now that packages and binaries are only built when needed, they need to be defined in both stages in case something building in the main stage needs something that was defined, but didn't need to be built in the earlier stage. Change-Id: I67704fba1d670e82218eba5ce91f0c01896557a2
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.