commit | ea376d6dc52aec7fd398ca8dd5154efbf37ca550 | [log] [tgz] |
---|---|---|
author | Lukacs T. Berki <lberki@google.com> | Wed Mar 24 17:44:29 2021 +0000 |
committer | Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com> | Wed Mar 24 17:44:29 2021 +0000 |
tree | 44032996d05cbc8cf0ca6e009aba2d722f242568 | |
parent | 40a7d4f9d2fe5f2b3bce5275e4375c4fef0a0feb [diff] | |
parent | 185ed798530b5669e396a0170cfb3782a33a043a [diff] |
Add an accessor function for the output Ninja file. am: a9ec69433d am: 584023ba01 am: 185ed79853 Original change: https://android-review.googlesource.com/c/platform/build/blueprint/+/1651769 Change-Id: I15228789ff0561c8a86cb9afff8634e2e843e774
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.