Merge remote-tracking branch 'aosp/upstream' into master

* aosp/upstream:
  Add Context.VisitDirectDeps

Test: builds
Change-Id: Ia66dde30a7af4d37aa0557341ab5d41953053cf1
tree: c7d3e3704e20fe44855adfdbc88e429b555187b1
  1. .gitignore
  2. .travis.fix-fork.sh
  3. .travis.gofmt.sh
  4. .travis.install-ninja.sh
  5. .travis.yml
  6. Blueprints
  7. CONTRIBUTING.md
  8. LICENSE
  9. README.md
  10. blueprint.bash
  11. bootstrap.bash
  12. bootstrap/
  13. bpfmt/
  14. bpmodify/
  15. build.ninja.in
  16. context.go
  17. context_test.go
  18. deptools/
  19. doc.go
  20. glob.go
  21. gotestmain/
  22. gotestrunner/
  23. live_tracker.go
  24. loadplugins/
  25. mangle.go
  26. module_ctx.go
  27. ninja_defs.go
  28. ninja_strings.go
  29. ninja_strings_test.go
  30. ninja_writer.go
  31. ninja_writer_test.go
  32. package_ctx.go
  33. parser/
  34. pathtools/
  35. proptools/
  36. scope.go
  37. singleton_ctx.go
  38. splice_modules_test.go
  39. tests/
  40. unpack.go
  41. unpack_test.go
  42. 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.