Gitiles
Code Review Sign In
review.blissroms.org / platform_build_blueprint / 2ca94325bf11bf8051ca6cfcffdffc236982baa6
commit2ca94325bf11bf8051ca6cfcffdffc236982baa6[log] [tgz]
authorJeff Gaston <jeffrygaston@google.com>Fri Oct 06 16:50:47 2017 -0700
committerJeff Gaston <jeffrygaston@google.com>Wed Oct 18 15:11:19 2017 -0700
tree9f1d4a2369a876ef242db91eaaeb363b51a0a4b5
parent6cd6ebc7681e2991ce57346d71952ae32f9a00ad [diff]
Have bpfmt show usage when run without any arguments

This is partially in hopes of making it generally easier to use, and
partially in hopes of specifically making it less tempting to do

bpfmt Android.bp > Android.bp

which actually would just erase the contents of Android.bp

Test: bpfmt Android.bp 2>&1 | grep usage && echo ok
Bug: 67326589
Change-Id: I41c23aca6214f27dbdf55e5931f9392c318e82ed
1 file changed
tree: 9f1d4a2369a876ef242db91eaaeb363b51a0a4b5
  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. package_ctx.go
  37. README.md
  38. scope.go
  39. singleton_ctx.go
  40. splice_modules_test.go
  41. unpack.go
  42. unpack_test.go
  43. 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.