Gitiles
Code Review Sign In
gerrit-public.fairphone.software / platform / build / blueprint / 66db8346ac274fa412f2fbea9fe9634a538a1b00
commit66db8346ac274fa412f2fbea9fe9634a538a1b00[log] [tgz]
authorDan Willemsen <dwillemsen@google.com>Sat Mar 03 02:53:40 2018 +0000
committerandroid-build-merger <android-build-merger@google.com>Sat Mar 03 02:53:40 2018 +0000
tree3340ea127569aae647095bbd16097b6bbe45ce12
parentcf4df9898d97f677131aabee11cb28b31157cb61 [diff]
parent02da469c2e51a2036fc8cfd8675ce5c646e42d1f [diff]
Merge remote-tracking branch 'aosp/upstream' am: db06ccbfa9
am: 02da469c2e

Change-Id: Ia0d9ee119db4a5483aebd860f3c1fc20eef72eec
tree: 3340ea127569aae647095bbd16097b6bbe45ce12
  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. LICENSE
  29. live_tracker.go
  30. mangle.go
  31. module_ctx.go
  32. name_interface.go
  33. ninja_defs.go
  34. ninja_strings.go
  35. ninja_strings_test.go
  36. ninja_writer.go
  37. ninja_writer_test.go
  38. OWNERS
  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.