Gitiles
Code Review Sign In
review.blissroms.org / platform_build_blueprint / 7dafbbcf6a756e40c58d0da6b306c9b3202218dd
commit7dafbbcf6a756e40c58d0da6b306c9b3202218dd[log] [tgz]
authorDan Willemsen <dwillemsen@google.com>Tue Jul 18 18:26:14 2017 -0700
committerDan Willemsen <dwillemsen@google.com>Mon Jul 24 14:02:15 2017 -0700
tree2d3ca97ce1c5565c0485176cb0a7d717cc39cd8b
parent7f2b2d229b2772828dcad18c8e566188fb488c2b [diff]
Add microfactory directly from Soong

From commit 38cef8ac3979da8e13037540981fe7aecc1e1fbe

Removes Go 1.7 from travis, since this depends on os.Executable

Change-Id: I58e2ae542621ffad66e9e145031091cb93ebb497
4 files changed
tree: 2d3ca97ce1c5565c0485176cb0a7d717cc39cd8b
  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. Blueprints
  20. bootstrap.bash
  21. build.ninja.in
  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. regen_build_ninja_in.sh
  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.