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

*   e8a09f9 Merge pull request #141 from colincross/fs
|\
| * b519a7e Add globbing to filesystem mocking
|/
* 2eeb7ee Merge pull request #140 from danw/sort_tests
* 61caa24 Sort testcases to make build (more) reproducible

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