No description
f5e34b98ca
"Variant" has been used to mean two slightly concepts in Blueprint. The first and most obvious is a variant of a module, meaning a list of all the ways that on version of a module differs from other versions of the same modules, for example "arch:arm, link:static". The other is for the specific way that a version of a module differs, "arch:arm". Rename all of uses of "variant" as the second meaning to "variation", and update the documentation to clarify "variant" vs. "variation". This modifies the build logic api to convert CreateVariants to CreateVariations. Change-Id: I789ef209ae6ddd39ec12e0c032f9f47f86698fe6 |
||
---|---|---|
bootstrap | ||
bpfmt | ||
bpmodify | ||
deptools | ||
parser | ||
pathtools | ||
proptools | ||
Blueprints | ||
bootstrap.bash | ||
build.ninja.in | ||
context.go | ||
context_test.go | ||
doc.go | ||
LICENSE | ||
live_tracker.go | ||
mangle.go | ||
module_ctx.go | ||
ninja_defs.go | ||
ninja_strings.go | ||
ninja_strings_test.go | ||
ninja_writer.go | ||
ninja_writer_test.go | ||
package_ctx.go | ||
README.md | ||
scope.go | ||
singleton_ctx.go | ||
unpack.go | ||
unpack_test.go |
Blueprint Build System
Blueprint is a meta-build system that reads in Blueprints files that describe modules that need to be built, and produces a Ninja (http://martine.github.io/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 langauge 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.