Gitiles
Code Review Sign In
review.blissroms.org / platform_build_blueprint / 20eab856abb6d44bdf7fdbef42f2494c0be4d19c
commit20eab856abb6d44bdf7fdbef42f2494c0be4d19c[log] [tgz]
authorJeff Gaston <jeffrygaston@google.com>Mon Dec 04 18:05:43 2017 -0800
committerJeff Gaston <jeffrygaston@google.com>Mon Dec 04 18:05:43 2017 -0800
tree7d6440c1524f0fb5bdbb1a074b31335a62a13fd1
parent058a24de5b93b58f8a74891d54edd117d98ad6ab [diff]
parent14978f8f9da86f73da0e97d662570bf0d2cdc188 [diff]
Merge remote-tracking branch 'aosp/upstream' into master

* aosp/upstream:
  Make ninja file deterministic even with dup module names
  Disallow bp 'build' includes to reference other dirs
  Pass ModulePath to NameInterface
  Have handleOneFile(child) wait for handleOneFile(parent).

Bug: 65683273
Test: see individual tests on the merged commits

Change-Id: Ifeb0b67f21d0ab90172a9a79ccebbef52d64f258
tree: 7d6440c1524f0fb5bdbb1a074b31335a62a13fd1
  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.