Gitiles
Code Review Sign In
review.blissroms.org / platform_build_blueprint / 40e4d10377ff21dea56a0d4040c1d44c4cb78d49
commit40e4d10377ff21dea56a0d4040c1d44c4cb78d49[log] [tgz]
authorColin Cross <ccross@android.com>Thu Jan 09 14:24:50 2020 -0800
committerColin Cross <ccross@android.com>Thu Jan 09 14:25:08 2020 -0800
tree74cca45317fd3463dc6a4d90fd41f20198f2b5b2
parent86286b9ac935c3d81d81044cc10d0d436ad09029 [diff]
parent5e8efd5f0852d3dad074efe63463fb334464f3c3 [diff]
Merge remote-tracking branch 'aosp/upstream' into master

* aosp/upstream:
  Allow primary builder to change working directory

Bug: 146437378
Test: m checkbuild
Change-Id: I95c476539cd2a74500b3f94baf048306ad5d9eca
tree: 74cca45317fd3463dc6a4d90fd41f20198f2b5b2
  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. glob_test.go
  28. go.mod
  29. LICENSE
  30. live_tracker.go
  31. mangle.go
  32. module_ctx.go
  33. module_ctx_test.go
  34. name_interface.go
  35. ninja_defs.go
  36. ninja_strings.go
  37. ninja_strings_test.go
  38. ninja_writer.go
  39. ninja_writer_test.go
  40. OWNERS
  41. package_ctx.go
  42. README.md
  43. scope.go
  44. singleton_ctx.go
  45. splice_modules_test.go
  46. 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.