No description
0e4607e788
The patch "Fix panic when dependency cycle includes the first module visited" caused cycles to print incorrectly by initializing the current module to be the last module in the cycle, when it should be the first module in the cycle. Change-Id: Iaf939283a48faa4cc6eeb9b19aed57993575a687 |
||
---|---|---|
bootstrap | ||
bpfmt | ||
bpmodify | ||
deptools | ||
parser | ||
pathtools | ||
proptools | ||
.travis.yml | ||
Blueprints | ||
bootstrap.bash | ||
build.ninja.in | ||
context.go | ||
context_test.go | ||
CONTRIBUTING.md | ||
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 | ||
splice_modules_test.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 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.