commit | 5f332c83aeca7d8b8a71cd5e2699feeb34e5e564 | [log] [tgz] |
---|---|---|
author | Jeff Gaston <jeffrygaston@google.com> | Wed Jun 28 15:10:11 2017 -0700 |
committer | Jeff Gaston <jeffrygaston@google.com> | Tue Sep 12 17:58:10 2017 -0700 |
tree | 7041a48ea220b07e6c21eb5996775fcdf0eeb14a | |
parent | 1ff2efa021f35f398882b0fdea34d2a6923e4f29 [diff] |
Move generated Travis test dirs outside the tree This should prevent the running of Travis tests from causing a filesystem loop src.test/test_tree/blueprint -> ../.. Bug: 63100441 Test: NINJA=... ./tests/test_tree_tests.sh; stat src.test 2>/dev/null \ && echo "src.test should not exist" Change-Id: Ie01fe8999c738dca166e3fabde9d9391f6b70210
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.