commit | 3802ba9f18c3586efa8e141f5a895b1ea9d4ae20 | [log] [tgz] |
---|---|---|
author | Jeff Gaston <jeffrygaston@google.com> | Mon Sep 11 16:36:07 2017 -0700 |
committer | Jeff Gaston <jeffrygaston@google.com> | Mon Oct 30 15:00:19 2017 -0700 |
tree | f5a120ba4fb30007a7295bd89049f09724670b4f | |
parent | c3e2844dfeba7f07ba10bd72730f649f82759150 [diff] |
No longer follow subdirs in Android.bp files because there some symlinks named Android.bp that point to files named Android.bp that contain <subdir> entries that are supposed to be interpreted relative to the original symlink. It's more convenient to just skip following subdirs. Bug: 64363847 Test: make -j Change-Id: Ib15f1d1c7d511191fd841b1a29ceed559dd6cdbb
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.