Google Git
Sign in
android / platform / build / blueprint / aeffbf7
commitaeffbf776abff483634d1fc1bba0abce15b6d72e[log] [tgz]
authorDan Willemsen <dwillemsen@google.com>Wed Nov 25 15:29:32 2015 -0800
committerDan Willemsen <dwillemsen@google.com>Mon Nov 30 17:03:34 2015 -0800
treef66d827ac5177a7b5dabe2d1137581f816a4488d
parent6afb72ff1bde8ad53bb0da4b85fa15e73e1bb1fe [diff]
Allow wrapping of PackageContext

Turn PackageContext into an interface so that build systems can wrap it
to add more custom helpers.

This does introduce an API change, though it should be fairly simple.
NewPackageContext used to provide an opaque *PackageContext struct, now it
provides a PackageContext interface.

Change-Id: I383c64a303d857ef5e0dec86ad77f791ba4c9639
7 files changed
tree: f66d827ac5177a7b5dabe2d1137581f816a4488d
  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
  14. .travis.fix-fork.sh
  15. .travis.install-ninja.sh
  16. .travis.yml
  17. Blueprints
  18. bootstrap.bash
  19. build.ninja.in
  20. context.go
  21. context_test.go
  22. context_test_Blueprints
  23. CONTRIBUTING.md
  24. doc.go
  25. LICENSE
  26. live_tracker.go
  27. mangle.go
  28. module_ctx.go
  29. ninja_defs.go
  30. ninja_strings.go
  31. ninja_strings_test.go
  32. ninja_writer.go
  33. ninja_writer_test.go
  34. package_ctx.go
  35. README.md
  36. scope.go
  37. singleton_ctx.go
  38. splice_modules_test.go
  39. unpack.go
  40. unpack_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.