Google Git
Sign in
android / platform / build / blueprint / refs/tags/platform-tools-30.0.5
tag51118ca26a5a1e79353b155b947b26e866264c77
taggerThe Android Open Source Project <initial-contribution@android.com>Wed Nov 04 12:13:48 2020 -0800
object4ea4f5b97970cb9d0d33de29b589deef24534e29 
Platform Tools Release 30.0.5 (6877874)
commit4ea4f5b97970cb9d0d33de29b589deef24534e29[log] [tgz]
authorandroid-build-prod (mdb) <android-build-team-robot@google.com>Thu Oct 01 20:31:56 2020 +0000
committerandroid-build-prod (mdb) <android-build-team-robot@google.com>Thu Oct 01 20:31:56 2020 +0000
treecef4043d9661ebb911504b5317d9dd19587f63a2
parent3aaee96fd2993eafc539c4e32defb7e3b8263c99 [diff]
parentf94644fe3d680095d6ac38d8333e76d3c64841ee [diff]
Snap for 6877830 from f94644fe3d680095d6ac38d8333e76d3c64841ee to sdk-release

Change-Id: I98a77c7c6768be20af639d3d4c0e4c192d3ff6bf
tree: cef4043d9661ebb911504b5317d9dd19587f63a2
  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. provider.go
  41. provider_test.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

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.