Gitiles
Code Review Sign In
review.blissroms.org / platform_build_blueprint / 9492c29702eac3112871d42c6978ccbe9c895d66
commit9492c29702eac3112871d42c6978ccbe9c895d66[log] [tgz]
authorColin Cross <ccross@android.com>Mon Dec 14 22:27:39 2020 +0000
committerAutomerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>Mon Dec 14 22:27:39 2020 +0000
treeb1bec8ecc80e846fed1d68973154c19c6a7aa8ae
parent14e63c229f8afd61d39c69a30353bcf242ea47e4 [diff]
parent52176e98518be598f45b6ec278d5c392a5a43acb [diff]
Merge remote-tracking branch 'aosp/upstream' am: 52176e9851

Original change: https://android-review.googlesource.com/c/platform/build/blueprint/+/1527662

MUST ONLY BE SUBMITTED BY AUTOMERGER

Change-Id: I836eb4971d005de6ca9144ea248790a0e5e86398
tree: b1bec8ecc80e846fed1d68973154c19c6a7aa8ae
  1. .github/
  2. bootstrap/
  3. bpfmt/
  4. bpmodify/
  5. deptools/
  6. gotestmain/
  7. gotestrunner/
  8. loadplugins/
  9. microfactory/
  10. parser/
  11. pathtools/
  12. proptools/
  13. tests/
  14. .gitignore
  15. .gofmt.sh
  16. blueprint.bash
  17. blueprint_impl.bash
  18. Blueprints
  19. bootstrap.bash
  20. CODEOWNERS
  21. context.go
  22. context_test.go
  23. CONTRIBUTING.md
  24. doc.go
  25. glob.go
  26. glob_test.go
  27. go.mod
  28. LICENSE
  29. live_tracker.go
  30. mangle.go
  31. module_ctx.go
  32. module_ctx_test.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. provider.go
  42. provider_test.go
  43. README.md
  44. scope.go
  45. singleton_ctx.go
  46. splice_modules_test.go
  47. visit_test.go
README.md

Blueprint Build System

build

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.