Fix error messages containing variable types

value.Type and value.Pos changed to methods, change the users that were
not caught by error checking to use Type() or Pos().

Change-Id: I295a658c007fa2de68c89fb85ee367fbea5ed1aa
2 files changed
tree: d62f7dab3e664992ba82c7767b4a148661c4cf09
  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
  16. .travis.yml
  17. blueprint.bash
  18. Blueprints
  19. bootstrap.bash
  21. context.go
  22. context_test.go
  23. context_test_Blueprints
  25. doc.go
  27. live_tracker.go
  28. mangle.go
  29. module_ctx.go
  30. ninja_defs.go
  31. ninja_strings.go
  32. ninja_strings_test.go
  33. ninja_writer.go
  34. ninja_writer_test.go
  35. package_ctx.go
  37. scope.go
  38. singleton_ctx.go
  39. splice_modules_test.go
  40. unpack.go
  41. unpack_test.go

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.