Gitiles
Code Review Sign In
review.blissroms.org / platform_build_blueprint / 8d7c363c122279d84ef179ddd31ce0a1cdf63525
commit8d7c363c122279d84ef179ddd31ce0a1cdf63525[log] [tgz]
authorColin Cross <ccross@android.com>Tue Mar 05 19:49:58 2019 -0800
committerandroid-build-merger <android-build-merger@google.com>Tue Mar 05 19:49:58 2019 -0800
tree4bcd21ef263fa06abceff63d69b3a86726c6bf94
parent065ac47e03d1d10e3a1be4c9c9236630c635d76b [diff]
parent8954814fb5d6ed6e0a55c9828b6397d50adb7f09 [diff]
Merge remote-tracking branch 'aosp/upstream' into master am: d8000d21a9
am: 8954814fb5

Change-Id: I02af9bbf9959d0aeac0bc6021acd52f96e4c51e3
tree: 4bcd21ef263fa06abceff63d69b3a86726c6bf94
  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. name_interface.go
  34. ninja_defs.go
  35. ninja_strings.go
  36. ninja_strings_test.go
  37. ninja_writer.go
  38. ninja_writer_test.go
  39. OWNERS
  40. package_ctx.go
  41. README.md
  42. scope.go
  43. singleton_ctx.go
  44. splice_modules_test.go
  45. unpack.go
  46. unpack_test.go
  47. 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.