Don't rely on deps property position

Dependency errors were prefixed with ??? because they were associated
with the position of the "deps" property, which is often not used.  Use
the position of the module instead.
1 file changed
tree: ae687d330885b825d7203cd51ea86cdd96b7ba96
  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. context_test_Blueprints
  23. CONTRIBUTING.md
  24. doc.go
  25. LICENSE
  26. live_tracker.go
  27. mangle.go
  28. module_ctx.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. README.md
  36. scope.go
  37. singleton_ctx.go
  38. splice_modules_test.go
  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.