Relax module naming restrictions

Forcing module names to be valid ninja names is an unnecessary
restraint on the project build logic.  Allow any string as a
module name, and sanitize and uniquify the module name for use
in module-scoped variables.

Also move the module scope to be per-module instead of per-group
so that modules can use the same local variable name for each variant.

Change-Id: If44cca20712305e2c0b6d6b39daa5eace335c148
3 files changed
tree: 1f7afa36d10536cbaa45e7eb62c47a2dc9962d99
  1. bootstrap/
  2. bpfmt/
  3. bpmodify/
  4. deptools/
  5. parser/
  6. pathtools/
  7. proptools/
  8. Blueprints
  9. bootstrap.bash
  10. build.ninja.in
  11. context.go
  12. context_test.go
  13. doc.go
  14. LICENSE
  15. live_tracker.go
  16. mangle.go
  17. module_ctx.go
  18. ninja_defs.go
  19. ninja_strings.go
  20. ninja_strings_test.go
  21. ninja_writer.go
  22. ninja_writer_test.go
  23. package_ctx.go
  24. README.md
  25. scope.go
  26. singleton_ctx.go
  27. unpack.go
  28. unpack_test.go
README.md

Blueprint Build System

Blueprint is a meta-build system that reads in Blueprints files that describe modules that need to be built, and produces a Ninja (http://martine.github.io/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 langauge 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.