Add walkDeps to context and module_ctx.

walkDeps performs a pre-order DFS (unlike visitDepsDepthFirst which is
a post-order DFS). The visit function takes in both a parent and child
node and returns a bool indicating if the child node should be
traversed.
2 files changed
tree: 4a2fc47545e5451f3b9376c2359cd44b862370e9
  1. bootstrap/
  2. bpfmt/
  3. bpmodify/
  4. choosestage/
  5. deptools/
  6. gotestmain/
  7. gotestrunner/
  8. loadplugins/
  9. parser/
  10. pathtools/
  11. proptools/
  12. tests/
  13. .gitignore
  14. .travis.fix-fork.sh
  15. .travis.install-ninja.sh
  16. .travis.yml
  17. Blueprints
  18. bootstrap.bash
  19. build.ninja.in
  20. context.go
  21. context_test.go
  22. CONTRIBUTING.md
  23. doc.go
  24. LICENSE
  25. live_tracker.go
  26. mangle.go
  27. module_ctx.go
  28. ninja_defs.go
  29. ninja_strings.go
  30. ninja_strings_test.go
  31. ninja_writer.go
  32. ninja_writer_test.go
  33. package_ctx.go
  34. README.md
  35. scope.go
  36. singleton_ctx.go
  37. splice_modules_test.go
  38. unpack.go
  39. unpack_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.