| commit | 21b6f37ceeb18a81e4e712d575d1f56a55775132 | [log] [tgz] |
|---|---|---|
| author | Dan Willemsen <dwillemsen@google.com> | Wed Jul 22 12:58:01 2015 -0700 |
| committer | Dan Willemsen <dwillemsen@google.com> | Wed Jul 22 15:51:52 2015 -0700 |
| tree | 34d75914f1e2bd73bfe8b30fd17e26c289e44554 | |
| parent | 958b3acd107aa679d6bc38a5658c439d9456d0e3 [diff] |
Require ninja 1.6.0, remove workaround The workaround no longer works with the new stage selector. We may run bootstrap.ninja.in twice before running the next stage, but we can't encode whether to run another ninja instance in the checked in build.ninja.in. This can likely be solved, but now that there's an official release with support for multiple passes, just push up the required version. Change-Id: I76e321912e323d60e462aabec61bdfcc7118cd5e
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.