Gitiles
Code Review Sign In
review.blissroms.org / platform_build_blueprint / 60bb204d8f5c88b77f95c2f80e200241a87dd311
commit60bb204d8f5c88b77f95c2f80e200241a87dd311[log] [tgz]
authorColin Cross <ccross@android.com>Fri Sep 11 20:19:57 2020 -0700
committerColin Cross <ccross@android.com>Fri Sep 11 20:20:41 2020 -0700
tree024346cc76ab1f4bfa5382c5e0733f4ec4aa606b
parent8dfb36edbf6be1b4cd09f3840bb74b068a1b710d [diff]
parent4b3efdc5b875cc79058c069fffa38ca65d4eb0ab [diff]
Merge remote-tracking branch 'aosp/upstream'

* aosp/upstream:
  Relax check in moduleMatchingVariant
  Fix AddFarVariationDependencies subset checks
  Maintain ordering between variants and aliases
  Add tests for findVariant

Test: m checkbuild
Change-Id: I4c166ff93a09fe4c6d700c82f79548f0b4afdae0
tree: 024346cc76ab1f4bfa5382c5e0733f4ec4aa606b
  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. context.go
  21. context_test.go
  22. CONTRIBUTING.md
  23. doc.go
  24. glob.go
  25. glob_test.go
  26. go.mod
  27. LICENSE
  28. live_tracker.go
  29. mangle.go
  30. module_ctx.go
  31. module_ctx_test.go
  32. name_interface.go
  33. ninja_defs.go
  34. ninja_strings.go
  35. ninja_strings_test.go
  36. ninja_writer.go
  37. ninja_writer_test.go
  38. OWNERS
  39. package_ctx.go
  40. README.md
  41. scope.go
  42. singleton_ctx.go
  43. splice_modules_test.go
  44. 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.