commit | 2a062a2ef03631110e29b9c415aa30e81a4c5614 | [log] [tgz] |
---|---|---|
author | Dan Willemsen <dwillemsen@google.com> | Sun Apr 19 13:32:06 2020 -0700 |
committer | GitHub <noreply@github.com> | Sun Apr 19 13:32:06 2020 -0700 |
tree | f814bd71c3ad87c833982781307be5b1353f243d | |
parent | 6957a46d38c98c6008f6f667281d219d7d6949dc [diff] | |
parent | 6c6c10361214f0bfe58578aa1de0207e255c8011 [diff] |
Merge pull request #296 from danw/emptyfile Actually write an empty ninja file with --empty-ninja-file
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.