No description
4d6af1f89e
With the introduction of $buildDir in bootstrapDir, the ninja cleanup step hasn't been able to cleanup during the bootstrap stages. The main stage was unaffected, as long as you were using "." as your buildDir. Change-Id: I277dd7864989f9052d96cab9ce377548a1391a80 |
||
---|---|---|
bootstrap | ||
bpfmt | ||
bpmodify | ||
choosestage | ||
deptools | ||
gotestmain | ||
parser | ||
pathtools | ||
proptools | ||
tests | ||
.gitignore | ||
.travis.fix-fork.sh | ||
.travis.install-ninja.sh | ||
.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.