| commit | 958b3acd107aa679d6bc38a5658c439d9456d0e3 | [log] [tgz] |
|---|---|---|
| author | Dan Willemsen <dwillemsen@google.com> | Mon Jul 20 15:55:37 2015 -0700 |
| committer | Dan Willemsen <dwillemsen@google.com> | Mon Jul 20 17:51:21 2015 -0700 |
| tree | 1c626dc747029820179e2f73debb4d8cf7ae2283 | |
| parent | 0894cbc1a9f0564e77dfbe74ed09d03bc7eaf30d [diff] |
Don't print module header if nothing is defined Modules may decide not to output any build definitions in some cases. Clean up the ninja file by not adding headers for empty sections. One particular usecase is my upcoming multi-stage bootstrapping - bootstrap_go_* will not output any rules in the first stage unless it's required to build the primary builder. Change-Id: I6a6b54da7e1702c63bfa736bcf8daf16956f9449
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.