Gitiles
Code Review Sign In
review.blissroms.org / platform_build_blueprint / da809330f8354b84a29921e94ae95ab8a771b56f
commitda809330f8354b84a29921e94ae95ab8a771b56f[log] [tgz]
authorDan Willemsen <dwillemsen@google.com>Mon Feb 26 15:42:23 2018 -0800
committerDan Willemsen <dwillemsen@google.com>Mon Feb 26 16:02:05 2018 -0800
tree49e895294a2a9631c73cdc540091daac7b050626
parentfbcbac6aa1c79f49ac59fafd5a0ee9de85008e16 [diff]
parent77dc4de53e0fe30ad27a340f00868b014b41d2eb [diff]
Merge remote-tracking branch 'aosp/upstream' into master

* aosp/upstream:
  Append / to directories in Glob results

Bug: 71906438
Test: out/soong/build.ninja is identical
Change-Id: Ic4c64015e9b6e70887fdc8c6f70b021b01886f1c
tree: 49e895294a2a9631c73cdc540091daac7b050626
  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.