|author||Dan Willemsen <email@example.com>||Thu Jan 14 15:42:54 2016 -0800|
|committer||Dan Willemsen <firstname.lastname@example.org>||Mon Mar 28 14:14:15 2016 -0700|
Add SingletonContext.Eval to evaluate ninja strings Our use case is to write out some configuration variables to give to our legacy build system. But in order to do that, we either need to keep a Go copy of all of the configuration, and still have all the calls to convert them to ninja variables, or evaluate our ninja variables. Change-Id: If9dda305ed41bc8aabe57dd750a74d8b9af1d1a4
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.