Google Git
Sign in
android / platform / build / blueprint / 28b2843b782e0b1b62a1c8d7a64dbae2fec5e76f
commit28b2843b782e0b1b62a1c8d7a64dbae2fec5e76f[log] [tgz]
authorColin Cross <ccross@android.com>Mon Dec 11 15:03:11 2017 -0800
committerColin Cross <ccross@android.com>Mon Dec 11 16:31:41 2017 -0800
tree7cece3c37ce8871b9d150a17021f35cc722221c5
parent5eb116a46e3c7cd4cd6de80b9f4e29a78ef420c2 [diff]
Allow primary builder to stop bootstrap early

Allow the primary builder to stop bootstrap between
ResolveDependencies and PrepareBuildActions so that it can
use the build graph to write customized documentation.

Change-Id: I67ee5e6e438a0c2c3ec844c4c453d223971e60a2
2 files changed
tree: 7cece3c37ce8871b9d150a17021f35cc722221c5
  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. package_ctx.go
  38. README.md
  39. scope.go
  40. singleton_ctx.go
  41. splice_modules_test.go
  42. unpack.go
  43. unpack_test.go
  44. 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.