Gitiles
Code Review Sign In
review.blissroms.org / platform_build_blueprint / 27f87af39f4f86375a4621e1389e5fc9604eeeb6
commit27f87af39f4f86375a4621e1389e5fc9604eeeb6[log] [tgz]
authorJeff Gaston <jeffrygaston@google.com>Wed Nov 22 22:47:10 2017 +0000
committerandroid-build-merger <android-build-merger@google.com>Wed Nov 22 22:47:10 2017 +0000
treebdd76d550ebba053ba3cbbe17aec6bc43d6ecc27
parent0685510e084f51437b39149b9ef1482ec4e496d2 [diff]
parent6601decd2dd92d9cb4e69499cbd57dae0925f3c7 [diff]
Merge remote-tracking branch 'aosp/upstream' into master am: 83cecbe4a6 am: 467126a895
am: 6601decd2d

Change-Id: Icd216d199b0f938f339488da51312cfdd16cbf82
tree: bdd76d550ebba053ba3cbbe17aec6bc43d6ecc27
  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. LICENSE
  28. live_tracker.go
  29. mangle.go
  30. module_ctx.go
  31. ninja_defs.go
  32. ninja_strings.go
  33. ninja_strings_test.go
  34. ninja_writer.go
  35. ninja_writer_test.go
  36. OWNERS
  37. package_ctx.go
  38. README.md
  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.