commit | a259945b744f6f367c24ff01594412ee8147d454 | [log] [tgz] |
---|---|---|
author | Colin Cross <ccross@android.com> | Wed Nov 18 16:01:01 2015 -0800 |
committer | Colin Cross <ccross@android.com> | Wed Nov 18 16:06:19 2015 -0800 |
tree | 8cfd9fb6fdbae411b88554e987cfdb19f49bd21b | |
parent | 01739302cbf3c26e28bd8dcecc7dc90ae0bbdfc0 [diff] |
Use context builddir for removing abandoned files Removing abandoned files needs to know where the .ninja_log file is stored. Export the ninja builddir value from Context and use it to determine the .ninja_log path in any stage. The ninja builddir (where ninja stores its .ninja_log and .ninja_deps files) and the bootstrap.BuildDir (where build output files are written) are distinct, so to reduce confusion replace SetBuildDir with SetNinjaBuildDir.
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.