Gitiles
Code Review Sign In
review.blissroms.org / platform_build_blueprint / 7d2e60ece75b03957b64d2223e267fe851be544e
commit7d2e60ece75b03957b64d2223e267fe851be544e[log] [tgz]
authorLukacs T. Berki <lberki@google.com>Mon Mar 08 16:47:28 2021 +0100
committerLukacs T. Berki <lberki@google.com>Mon Mar 08 16:48:38 2021 +0100
tree29d7ab9c4c886e2486af6fd77a829a6a7bf7400e
parent122b3ee153775588fac64a8bd679c6fae265a9f7 [diff]
Use stageDir() to determine the install directory.

In particular, for Go binary modules.

Test: Manual ("m nothing")
Change-Id: I98d184a00f1a48bc68e4b03747331fd449e37de1
1 file changed
tree: 29d7ab9c4c886e2486af6fd77a829a6a7bf7400e
  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. CODEOWNERS
  21. context.go
  22. context_test.go
  23. CONTRIBUTING.md
  24. doc.go
  25. glob.go
  26. glob_test.go
  27. go.mod
  28. LICENSE
  29. live_tracker.go
  30. mangle.go
  31. module_ctx.go
  32. module_ctx_test.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. PREUPLOAD.cfg
  42. provider.go
  43. provider_test.go
  44. README.md
  45. scope.go
  46. singleton_ctx.go
  47. splice_modules_test.go
  48. 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.