Google Git
Sign in
android / platform / build / blueprint / 10b473fefacd57c33d442767332780b3d6857ef5
commit10b473fefacd57c33d442767332780b3d6857ef5[log] [tgz]
authorChris Parsons <cparsons@google.com>Tue Jun 16 13:01:47 2020 -0400
committerChris Parsons <cparsons@google.com>Tue Jun 16 13:02:55 2020 -0400
tree067b3f13f718dd33ed1509e98ee078e569139ff1
parentf7f790fe7571f7123d8fa397085d584c4a3ba99d [diff]
parent2c0cd0ac8ded67ef06a247799187dad58b8ae5cd [diff]
Merge remote-tracking branch 'aosp/upstream' into pull-upstream-2

* aosp/upstream:
  Use github actions instead of travis
  Export ModuleListFile in bootstrap (with fix) (#304)
  Revert "Merge pull request #301 from c-parsons/modulelistfile"
  Revert "Always emit rules for tests and add phony to run them"
  Revert changes to singleton_ctx.go
  Change bootstrap.moduleListFile to be exported
  Add a getter for ModuleListFile to SingletonContext

Test: `m nothing` and treehugger
Change-Id: I37cb1b08d962ab34d3b7d7999496795986315217
tree: 067b3f13f718dd33ed1509e98ee078e569139ff1
  1. .github/
  2. bootstrap/
  3. bpfmt/
  4. bpmodify/
  5. deptools/
  6. gotestmain/
  7. gotestrunner/
  8. loadplugins/
  9. microfactory/
  10. parser/
  11. pathtools/
  12. proptools/
  13. tests/
  14. .gitignore
  15. .gofmt.sh
  16. blueprint.bash
  17. blueprint_impl.bash
  18. Blueprints
  19. bootstrap.bash
  20. context.go
  21. context_test.go
  22. CONTRIBUTING.md
  23. doc.go
  24. glob.go
  25. glob_test.go
  26. go.mod
  27. LICENSE
  28. live_tracker.go
  29. mangle.go
  30. module_ctx.go
  31. module_ctx_test.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. visit_test.go
README.md

Blueprint Build System

build

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.