Fix cycle printing

The patch "Fix panic when dependency cycle includes the first
module visited" caused cycles to print incorrectly by initializing
the current module to be the last module in the cycle, when it
should be the first module in the cycle.

Change-Id: Iaf939283a48faa4cc6eeb9b19aed57993575a687
1 file changed
tree: d8c2cdeaee0aa6e634835cf0f7e503e49f17bdaa
  1. bootstrap/
  2. bpfmt/
  3. bpmodify/
  4. deptools/
  5. parser/
  6. pathtools/
  7. proptools/
  8. .travis.yml
  9. Blueprints
  10. bootstrap.bash
  11. build.ninja.in
  12. context.go
  13. context_test.go
  14. CONTRIBUTING.md
  15. doc.go
  16. LICENSE
  17. live_tracker.go
  18. mangle.go
  19. module_ctx.go
  20. ninja_defs.go
  21. ninja_strings.go
  22. ninja_strings_test.go
  23. ninja_writer.go
  24. ninja_writer_test.go
  25. package_ctx.go
  26. README.md
  27. scope.go
  28. singleton_ctx.go
  29. splice_modules_test.go
  30. unpack.go
  31. 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.