Gitiles
Code Review Sign In
review.blissroms.org / platform_build_blueprint / 4db5a3f78394ffd54da082c11526b7722df7725e
commit4db5a3f78394ffd54da082c11526b7722df7725e[log] [tgz]
authorJeff Gaston <jeffrygaston@google.com>Tue Dec 05 17:08:15 2017 -0800
committerJeff Gaston <jeffrygaston@google.com>Tue Dec 05 17:08:35 2017 -0800
treeea6a2938846e709b6d83f038cebf2f883b5fc5a8
parent20eab856abb6d44bdf7fdbef42f2494c0be4d19c [diff]
parent7a88d0db4d06b39809e6915f27063bd704a948e7 [diff]
Merge remote-tracking branch 'aosp/upstream' into master

* aosp/upstream:
  prevent file=nil panic if syntax error in Blueprints
  have openAndParse use return values rather than channels
  rename parseOneAsync to openAndParse
  Update microfactory compile error message to show the command that failed

Test: see tests on individual commits

Change-Id: I5faa4c8f5bc1a3845f7c7fcdbd5edb8d4e000acc
tree: ea6a2938846e709b6d83f038cebf2f883b5fc5a8
  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. name_interface.go
  32. ninja_defs.go
  33. ninja_strings.go
  34. ninja_strings_test.go
  35. ninja_writer.go
  36. ninja_writer_test.go
  37. OWNERS
  38. package_ctx.go
  39. README.md
  40. scope.go
  41. singleton_ctx.go
  42. splice_modules_test.go
  43. unpack.go
  44. unpack_test.go
  45. 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.