Gitiles
Code Review Sign In
gerrit-public.fairphone.software / platform / build / blueprint / f8f0592fa215ba0ef6d64935ec19974a318eec7d
commitf8f0592fa215ba0ef6d64935ec19974a318eec7d[log] [tgz]
authorBill Yi <byi@google.com>Wed Oct 24 10:30:00 2018 -0700
committerandroid-build-merger <android-build-merger@google.com>Wed Oct 24 10:30:00 2018 -0700
tree589b28e6bbf8a8f9c3d26d5b3614552a70bc21a5
parent5cf11767fa8402deefeca9e4e3f6711642bdcbe0 [diff]
parentce07e5e424ab6c98215403ab2b447e8196cbccb3 [diff]
[automerger skipped] Merge pi-platform-release to stage-aosp-master - DO NOT MERGE am: 87f861d737  -s ours
am: ce07e5e424  -s ours

Change-Id: I0b6131c959b80d7bb1c7d076ecb9b4d251d69ebb
tree: 589b28e6bbf8a8f9c3d26d5b3614552a70bc21a5
  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. OWNERS
  40. package_ctx.go
  41. README.md
  42. scope.go
  43. singleton_ctx.go
  44. splice_modules_test.go
  45. unpack.go
  46. unpack_test.go
  47. 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.