Gitiles
Code Review Sign In
review.blissroms.org / platform_build_blueprint / a9cb75732882dee5595d30aa549e81446645710b
commita9cb75732882dee5595d30aa549e81446645710b[log] [tgz]
authorColin Cross <ccross@android.com>Thu Jun 28 13:12:44 2018 -0700
committerandroid-build-merger <android-build-merger@google.com>Thu Jun 28 13:12:44 2018 -0700
tree336c43dca2704643e71d7e3226852ffd8447adce
parentbe0010ccbbe32a8671ce4a041940ccafec6dd2f7 [diff]
parented3fd6ba19edfc2be28f0c2d9954603934d2b8a8 [diff]
Merge remote-tracking branch 'aosp/upstream'
am: ed3fd6ba19

Change-Id: I9a78ba4fca2a2c04edbd8c58a5256157499638ed
tree: 336c43dca2704643e71d7e3226852ffd8447adce
  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. glob_test.go
  28. LICENSE
  29. live_tracker.go
  30. mangle.go
  31. module_ctx.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. unpack.go
  45. unpack_test.go
  46. 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.