Gitiles
Code Review Sign In
review.blissroms.org / platform_build_blueprint / bb689ff5eda40bdcd5be7ebb0dee7f17161dfa37
commitbb689ff5eda40bdcd5be7ebb0dee7f17161dfa37[log] [tgz]
authorandroid-build-team Robot <android-build-team-robot@google.com>Wed Dec 13 08:23:58 2017 +0000
committerandroid-build-team Robot <android-build-team-robot@google.com>Wed Dec 13 08:23:58 2017 +0000
tree839af2c6405366a9951c0eb6bcf616a33e982de6
parent1cd0c6659981d1be12e4185b9d3323b891ae221c [diff]
parent84d833aec147f97a7d35716f7577ba99e0dd9d3c [diff]
Snap for 4500033 from 84d833aec147f97a7d35716f7577ba99e0dd9d3c to pi-release

Change-Id: Ia3378e0737c19e35475b5a2da53ab648a2735cb0
tree: 839af2c6405366a9951c0eb6bcf616a33e982de6
  1. bootstrap/
  2. bpfmt/
  3. bpmodify/
  4. deptools/
  5. gotestmain/
  6. gotestrunner/
  7. loadplugins/
  8. microfactory/
  9. parser/
  10. pathtools/
  11. proptools/
  12. tests/
  13. .gitignore
  14. .travis.fix-fork.sh
  15. .travis.gofmt.sh
  16. .travis.install-ninja.sh
  17. .travis.yml
  18. blueprint.bash
  19. blueprint_impl.bash
  20. Blueprints
  21. bootstrap.bash
  22. context.go
  23. context_test.go
  24. CONTRIBUTING.md
  25. doc.go
  26. glob.go
  27. LICENSE
  28. live_tracker.go
  29. mangle.go
  30. module_ctx.go
  31. name_interface.go
  32. ninja_defs.go
  33. ninja_strings.go
  34. ninja_strings_test.go
  35. ninja_writer.go
  36. ninja_writer_test.go
  37. OWNERS
  38. package_ctx.go
  39. README.md
  40. scope.go
  41. singleton_ctx.go
  42. splice_modules_test.go
  43. unpack.go
  44. unpack_test.go
  45. visit_test.go
README.md

Blueprint Build System

Build Status

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.