Gitiles
Code Review Sign In
review.blissroms.org / platform_build_blueprint / 7bcc256daced91c588fd03ad71f51d184ec44a1b
commit7bcc256daced91c588fd03ad71f51d184ec44a1b[log] [tgz]
authorColin Cross <ccross@android.com>Mon May 20 14:51:55 2019 -0700
committerColin Cross <ccross@android.com>Mon May 20 15:08:39 2019 -0700
treea620a20e84593f9f6f2e9ed926fa785a9132f005
parent99bdb2ab4fd5168a71a20aecf10611425be47ec4 [diff]
Move module and singleton godoc from the implementation to the interface

The interface is visible in godoc, not the implementation, so
move the documentation onto the interface methods.

Test: view godoc
Change-Id: I3460003eed6bf57d8ae4dabe70ab306f049a0060
2 files changed
tree: a620a20e84593f9f6f2e9ed926fa785a9132f005
  1. bootstrap/
  2. bpfmt/
  3. bpmodify/
  4. deptools/
  5. gotestmain/
  6. gotestrunner/
  7. loadplugins/
  8. microfactory/
  9. parser/
  10. pathtools/
  11. proptools/
  12. tests/
  13. .gitignore
  14. .travis.fix-fork.sh
  15. .travis.gofmt.sh
  16. .travis.install-ninja.sh
  17. .travis.yml
  18. blueprint.bash
  19. blueprint_impl.bash
  20. Blueprints
  21. bootstrap.bash
  22. context.go
  23. context_test.go
  24. CONTRIBUTING.md
  25. doc.go
  26. glob.go
  27. glob_test.go
  28. go.mod
  29. LICENSE
  30. live_tracker.go
  31. mangle.go
  32. module_ctx.go
  33. name_interface.go
  34. ninja_defs.go
  35. ninja_strings.go
  36. ninja_strings_test.go
  37. ninja_writer.go
  38. ninja_writer_test.go
  39. package_ctx.go
  40. README.md
  41. scope.go
  42. singleton_ctx.go
  43. splice_modules_test.go
  44. unpack.go
  45. unpack_test.go
  46. visit_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.