Google Git
Sign in
android / platform / build / blueprint / b11c0bacea76df518c4445671da74f0dc93a953d
commitb11c0bacea76df518c4445671da74f0dc93a953d[log] [tgz]
authorColin Cross <ccross@android.com>Mon Oct 23 15:05:58 2017 -0700
committerColin Cross <ccross@android.com>Mon Oct 23 15:06:02 2017 -0700
tree3f11f3281e7cf71ca92444740052aa1e2386a119
parentcb72d665707a2c14661159b7527f8f3adc1209bd [diff]
parentc63f1fd784d138fa9d4e9a5af8c7d851c349a715 [diff]
Merge remote-tracking branch 'aosp/upstream' into master

* aosp/upstream:
  Finish switching blueprint back to the original Blueprints format
  Have bpfmt show usage when run without any arguments
  Refactor in preparation to detect when stdout is the input file
  Add file locking to microfactory
  Utils to support removing duplicate shared_libs

Test: m checkbuild
Change-Id: Ibeb8e48a6c0fa3669e78d034bff89ba6faa6ccc4
tree: 3f11f3281e7cf71ca92444740052aa1e2386a119
  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. LICENSE
  28. live_tracker.go
  29. mangle.go
  30. module_ctx.go
  31. ninja_defs.go
  32. ninja_strings.go
  33. ninja_strings_test.go
  34. ninja_writer.go
  35. ninja_writer_test.go
  36. OWNERS
  37. package_ctx.go
  38. README.md
  39. scope.go
  40. singleton_ctx.go
  41. splice_modules_test.go
  42. unpack.go
  43. unpack_test.go
  44. 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.