commit | de7afaaf749957b3b7c03036e36c99a5ac7e3afb | [log] [tgz] |
---|---|---|
author | Colin Cross <ccross@android.com> | Wed Jan 23 13:23:00 2019 -0800 |
committer | Colin Cross <ccross@android.com> | Wed Jan 23 13:26:42 2019 -0800 |
tree | 252b6d360e85ef51166c3d7ac3ee090f887a02d0 | |
parent | 3a8c0256480255efdebd738238084cc9d6bf2b54 [diff] |
Write ninja file directly to the output file Writing the ninja file to a byte buffer causes a significant amount of time to be spent in memmove when growing the byte slice. Write the file directly to disk instead. This also fixes some unhandled error warnings, which become more likely when doing disk IO instead of byte buffer writes. Change-Id: I5094e4c45cab4012713037f60c5a4fb00718f92e
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.