Home | History | Annotate | only in /build/blueprint
Up to higher level directory
NameDateSize
.gitignore06-Dec-201718
.travis.fix-fork.sh06-Dec-2017213
.travis.gofmt.sh06-Dec-2017111
.travis.install-ninja.sh06-Dec-2017445
.travis.yml06-Dec-2017473
blueprint.bash06-Dec-20172.2K
Blueprints06-Dec-20173.9K
bootstrap/06-Dec-2017
bootstrap.bash06-Dec-20174.8K
bpfmt/06-Dec-2017
bpmodify/06-Dec-2017
build.ninja.in06-Dec-201717.4K
context.go06-Dec-201783.4K
context_test.go06-Dec-20174.2K
CONTRIBUTING.md06-Dec-20171.4K
deptools/06-Dec-2017
doc.go06-Dec-20173.4K
glob.go06-Dec-20172.7K
gotestmain/06-Dec-2017
gotestrunner/06-Dec-2017
LICENSE06-Dec-201711.1K
live_tracker.go06-Dec-20174.1K
loadplugins/06-Dec-2017
mangle.go06-Dec-2017910
module_ctx.go06-Dec-201723.6K
ninja_defs.go06-Dec-201711.2K
ninja_strings.go06-Dec-20179.1K
ninja_strings_test.go06-Dec-20173.9K
ninja_writer.go06-Dec-20175.5K
ninja_writer_test.go06-Dec-20172.6K
OWNERS06-Dec-201741
package_ctx.go06-Dec-201724.5K
parser/06-Dec-2017
pathtools/06-Dec-2017
proptools/06-Dec-2017
README.md06-Dec-2017854
regen_build_ninja_in.sh06-Dec-2017497
scope.go06-Dec-20179.3K
singleton_ctx.go06-Dec-20176.7K
splice_modules_test.go06-Dec-20174.5K
tests/06-Dec-2017
unpack.go06-Dec-201711.2K
unpack_test.go06-Dec-20179K
visit_test.go06-Dec-20173.8K

README.md

      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