commit | 1fef536ea6ed1dabc8b0180aa9ccbcdb0272cabe | [log] [tgz] |
---|---|---|
author | Colin Cross <ccross@android.com> | Mon Apr 20 16:50:54 2015 -0700 |
committer | Colin Cross <ccross@android.com> | Mon Apr 20 17:25:17 2015 -0700 |
tree | fe1cb3ff3305efa1e846a3605e4f30099c5ba6f2 | |
parent | 63d5d4d9e4fc62b5eefb96c461c2d02349b57ed8 [diff] |
Add support for build= variable build is a magic variable that acts similarly to subdirs, but specifies files to build instead of subdirs. Using files provides a few advantages: files can be named something more appropriate for the project than "Blueprints", whatever you want instead of Blueprints, and multiple Blueprints files can exist in the same directory. A new variable is used instead of putting filenames into subdirs to avoid unexpected behavior when a glob matches both files and directories. subdirs= and build= entries that don't match any directories or files are now reported as errors. Change-Id: Id329504ace251eab4ccea1081a3c8665a4c52f5a
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.