Add ModuleSubDir to Context and SingletonContext

Singletons may need ModuleSubDir, for example to implement a stable sort
on modules.  Add ModuleSubDir to SingletonContext and Context.
2 files changed
tree: bf0c3751337c3346056489776428cce5d200f2c2
  1. .gitignore
  2. .travis.fix-fork.sh
  3. .travis.install-ninja.sh
  4. .travis.yml
  5. Blueprints
  6. CONTRIBUTING.md
  7. LICENSE
  8. README.md
  9. bootstrap.bash
  10. bootstrap/
  11. bpfmt/
  12. bpmodify/
  13. build.ninja.in
  14. choosestage/
  15. context.go
  16. context_test.go
  17. context_test_Blueprints
  18. deptools/
  19. doc.go
  20. gotestmain/
  21. gotestrunner/
  22. live_tracker.go
  23. loadplugins/
  24. mangle.go
  25. module_ctx.go
  26. ninja_defs.go
  27. ninja_strings.go
  28. ninja_strings_test.go
  29. ninja_writer.go
  30. ninja_writer_test.go
  31. package_ctx.go
  32. parser/
  33. pathtools/
  34. proptools/
  35. scope.go
  36. singleton_ctx.go
  37. splice_modules_test.go
  38. tests/
  39. unpack.go
  40. 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.