Have handleOneFile(child) wait for handleOneFile(parent).

Bug: 65683273
Test: m -j nothing # which runs unit tests

Change-Id: I850e78ebcdbee68637f66d81fc127f19dd28508a
2 files changed
tree: d3288d08fd66ecddea8c7a630db4697b8699eeb2
  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. blueprint_impl.bash
  12. bootstrap.bash
  13. bootstrap/
  14. bpfmt/
  15. bpmodify/
  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. microfactory/
  27. module_ctx.go
  28. name_interface.go
  29. ninja_defs.go
  30. ninja_strings.go
  31. ninja_strings_test.go
  32. ninja_writer.go
  33. ninja_writer_test.go
  34. package_ctx.go
  35. parser/
  36. pathtools/
  37. proptools/
  38. scope.go
  39. singleton_ctx.go
  40. splice_modules_test.go
  41. tests/
  42. unpack.go
  43. unpack_test.go
  44. 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.