Gitiles
Code Review Sign In
gerrit-public.fairphone.software / platform / build / blueprint / 9033c957b95bd06736518c9d8f1d53e9c3be4567
commit9033c957b95bd06736518c9d8f1d53e9c3be4567[log] [tgz]
authorHunter Knepshield <hknepshield@google.com>Wed Feb 17 20:21:42 2021 -0800
committerHunter Knepshield <hknepshield@google.com>Wed Feb 17 20:24:50 2021 -0800
tree764a23cbacd2f9a10fcc79d7e15e85498c0caece
parente980b25b954389a6e4a2d96aa8c696a47d99c776 [diff]
Make bpfmt use exit codes even when reading from stdin.

Previously, an incantation like `bpfmt -o <$BAD_BP` would print to
stderr as expected, but then it would exit with 0. This is different
than the behavior of `bpfmt -o $BAD_BP`, which correctly exits with a
non-zero status code (in addition to printing the issues to stderr).

Test: m bpfmt; out/soong/host/linux-x86/bin/bpfmt -o <$BAD_BP; echo $?
Change-Id: I0a970cddf94fbd818525f9167d9113086b023c81
1 file changed
tree: 764a23cbacd2f9a10fcc79d7e15e85498c0caece
  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. provider.go
  42. provider_test.go
  43. README.md
  44. scope.go
  45. singleton_ctx.go
  46. splice_modules_test.go
  47. 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.