Add a flag to compile Go code for debugging.

This makes it possible to debug the primary builder without manually
adding the respective flags to the compilation command lines.

Test: "m nothing", "m nothing" with debugging, then "m nothing" again
Change-Id: I7d403af48528a94e5e0033d9a5c1fa9981100cfd
2 files changed
tree: c885819fdf16f56984c7fd1e2d0cd64b11f86b1c
  1. .github/
  2. .gitignore
  3. .gofmt.sh
  4. Blueprints
  5. CODEOWNERS
  6. CONTRIBUTING.md
  7. LICENSE
  8. OWNERS
  9. PREUPLOAD.cfg
  10. README.md
  11. blueprint.bash
  12. blueprint_impl.bash
  13. bootstrap.bash
  14. bootstrap/
  15. bpfmt/
  16. bpmodify/
  17. context.go
  18. context_test.go
  19. deptools/
  20. doc.go
  21. glob.go
  22. glob_test.go
  23. go.mod
  24. gotestmain/
  25. gotestrunner/
  26. live_tracker.go
  27. loadplugins/
  28. mangle.go
  29. microfactory/
  30. module_ctx.go
  31. module_ctx_test.go
  32. name_interface.go
  33. ninja_defs.go
  34. ninja_strings.go
  35. ninja_strings_test.go
  36. ninja_writer.go
  37. ninja_writer_test.go
  38. package_ctx.go
  39. parser/
  40. pathtools/
  41. proptools/
  42. provider.go
  43. provider_test.go
  44. scope.go
  45. singleton_ctx.go
  46. splice_modules_test.go
  47. tests/
  48. visit_test.go
README.md

Blueprint Build System

build

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.