Google Git
Sign in
android / platform / build / blueprint / android-8.1.0_r31
tagcc33c46b11d3a5a009f2b6633fb4a1e6ac02dea5
taggerThe Android Open Source Project <initial-contribution@android.com>Mon Jun 04 10:25:00 2018 -0700
objecta011038d864e3faa528ec1037a568e5824955a0f 
Android 8.1.0 release 31
commita011038d864e3faa528ec1037a568e5824955a0f[log] [tgz]
authorandroid-build-team Robot <android-build-team-robot@google.com>Wed Jul 19 07:24:43 2017 +0000
committerandroid-build-team Robot <android-build-team-robot@google.com>Wed Jul 19 07:24:43 2017 +0000
treef905bf359170436f22d818dd47a2ddbeb5a96d17
parent258cc0be9bcc5aa02064fb64d9ab7e195215155f [diff]
parent0eb7ed380ced72501305b14db3111df05cfb1069 [diff]
release-request-bd6aa7dd-7b02-4794-942c-14599bf61208-for-git_oc-mr1-release-4193791 snap-temp-L98700000083613807

Change-Id: I96265329a0b73b0379aa076ee3c55b16082e3f35
tree: f905bf359170436f22d818dd47a2ddbeb5a96d17
  1. bootstrap/
  2. bpfmt/
  3. bpmodify/
  4. deptools/
  5. gotestmain/
  6. gotestrunner/
  7. loadplugins/
  8. parser/
  9. pathtools/
  10. proptools/
  11. tests/
  12. .gitignore
  13. .travis.fix-fork.sh
  14. .travis.gofmt.sh
  15. .travis.install-ninja.sh
  16. .travis.yml
  17. blueprint.bash
  18. Blueprints
  19. bootstrap.bash
  20. build.ninja.in
  21. context.go
  22. context_test.go
  23. CONTRIBUTING.md
  24. doc.go
  25. glob.go
  26. LICENSE
  27. live_tracker.go
  28. mangle.go
  29. module_ctx.go
  30. ninja_defs.go
  31. ninja_strings.go
  32. ninja_strings_test.go
  33. ninja_writer.go
  34. ninja_writer_test.go
  35. OWNERS
  36. package_ctx.go
  37. README.md
  38. regen_build_ninja_in.sh
  39. scope.go
  40. singleton_ctx.go
  41. splice_modules_test.go
  42. unpack.go
  43. unpack_test.go
  44. 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.