Up to higher level directory | |||
Name | Date | Size | |
---|---|---|---|
.gitignore | 05-Oct-2017 | 18 | |
.travis.fix-fork.sh | 05-Oct-2017 | 213 | |
.travis.gofmt.sh | 05-Oct-2017 | 111 | |
.travis.install-ninja.sh | 05-Oct-2017 | 445 | |
.travis.yml | 05-Oct-2017 | 461 | |
blueprint.bash | 05-Oct-2017 | 2.2K | |
Blueprints | 05-Oct-2017 | 3.5K | |
bootstrap/ | 05-Oct-2017 | ||
bootstrap.bash | 05-Oct-2017 | 4.8K | |
bpfmt/ | 05-Oct-2017 | ||
bpmodify/ | 05-Oct-2017 | ||
build.ninja.in | 05-Oct-2017 | 16.6K | |
context.go | 05-Oct-2017 | 83.1K | |
context_test.go | 05-Oct-2017 | 4.2K | |
CONTRIBUTING.md | 05-Oct-2017 | 1.4K | |
deptools/ | 05-Oct-2017 | ||
doc.go | 05-Oct-2017 | 3.4K | |
glob.go | 05-Oct-2017 | 2.7K | |
gotestmain/ | 05-Oct-2017 | ||
gotestrunner/ | 05-Oct-2017 | ||
LICENSE | 05-Oct-2017 | 11.1K | |
live_tracker.go | 05-Oct-2017 | 4K | |
loadplugins/ | 05-Oct-2017 | ||
mangle.go | 05-Oct-2017 | 910 | |
module_ctx.go | 05-Oct-2017 | 23.6K | |
ninja_defs.go | 05-Oct-2017 | 10.9K | |
ninja_strings.go | 05-Oct-2017 | 8.8K | |
ninja_strings_test.go | 05-Oct-2017 | 3.9K | |
ninja_writer.go | 05-Oct-2017 | 5.5K | |
ninja_writer_test.go | 05-Oct-2017 | 2.6K | |
package_ctx.go | 05-Oct-2017 | 24.5K | |
parser/ | 05-Oct-2017 | ||
pathtools/ | 05-Oct-2017 | ||
proptools/ | 05-Oct-2017 | ||
README.md | 05-Oct-2017 | 854 | |
scope.go | 05-Oct-2017 | 9.3K | |
singleton_ctx.go | 05-Oct-2017 | 6.7K | |
splice_modules_test.go | 05-Oct-2017 | 4.5K | |
tests/ | 05-Oct-2017 | ||
unpack.go | 05-Oct-2017 | 11.2K | |
unpack_test.go | 05-Oct-2017 | 9K | |
visit_test.go | 05-Oct-2017 | 3.8K |
1 Blueprint Build System 2 ====================== 3 [![Build Status](https://travis-ci.org/google/blueprint.svg?branch=master)](https://travis-ci.org/google/blueprint) 4 5 Blueprint is a meta-build system that reads in Blueprints files that describe 6 modules that need to be built, and produces a 7 [Ninja](https://ninja-build.org/) manifest describing the commands that 8 need to be run and their dependencies. Where most build systems use built-in 9 rules or a domain-specific language to describe the logic for converting module 10 descriptions to build rules, Blueprint delegates this to per-project build 11 logic written in Go. For large, heterogenous projects this allows the inherent 12 complexity of the build logic to be maintained in a high-level language, while 13 still allowing simple changes to individual modules by modifying easy to 14 understand Blueprints files. 15