Gitiles
Code Review Sign In
review.evervolv.com / android_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. .gitignore
  2. .travis.fix-fork.sh
  3. .travis.gofmt.sh
  4. .travis.install-ninja.sh
  5. .travis.yml
  6. Blueprints
  7. CONTRIBUTING.md
  8. LICENSE
  9. README.md
  10. blueprint.bash
  11. blueprint_impl.bash
  12. bootstrap.bash
  13. bootstrap/
  14. bpfmt/
  15. bpmodify/
  16. context.go
  17. context_test.go
  18. deptools/
  19. doc.go
  20. glob.go
  21. glob_test.go
  22. go.mod
  23. gotestmain/
  24. gotestrunner/
  25. live_tracker.go
  26. loadplugins/
  27. mangle.go
  28. microfactory/
  29. module_ctx.go
  30. name_interface.go
  31. ninja_defs.go
  32. ninja_strings.go
  33. ninja_strings_test.go
  34. ninja_writer.go
  35. ninja_writer_test.go
  36. package_ctx.go
  37. parser/
  38. pathtools/
  39. proptools/
  40. scope.go
  41. singleton_ctx.go
  42. splice_modules_test.go
  43. tests/
  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.