commit | 5e40f19865428d8235ff2e245cde245fe252cf54 | [log] [tgz] |
---|---|---|
author | Chih-Hung Hsieh <chh@google.com> | Thu Jun 15 13:49:45 2017 -0700 |
committer | Chih-Hung Hsieh <chh@google.com> | Thu Jun 15 13:49:45 2017 -0700 |
tree | 326fb46de943a097835ec39a1c50b23012e5a029 | |
parent | e257cf82bdb9c5c1c35969e1977470fb6fb96837 [diff] |
Add OWNERS in build/blueprint * Owners are selected from top CL approvals or owners. They will be suggested to review/approve future CLs. * OWNERS files are recognized by the new find-owners plugin, see .md files in https://gerrit.googlesource.com/plugins/find-owners/+/master/src/main/resources/Documentation/ Test: build/make/tools/checkowners.py -c -v OWNERS Change-Id: I2b4cafabffcfa3668aa12f323b2e91e66ffc2ada
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.