Google Git
Sign in
fuchsia / third_party / blueprint / 036a1df37488b1704c59a74260ca3811f7188fd5
commit036a1df37488b1704c59a74260ca3811f7188fd5[log] [tgz]
authorColin Cross <ccross@android.com>Thu Dec 17 15:49:30 2015 -0800
committerColin Cross <ccross@android.com>Thu Dec 17 17:26:20 2015 -0800
tree959fd176f2068e9ce4f1a91c87aa72846711fade
parenteb97a6e7a1afa6d4817545bec3304e906ecc35f7 [diff]
Allow primary builder to handle missing dependencies

In some cases the primary builder may need to handle missing
dependencies.  Add Context.SetAllowMissingDependencies to cause
Blueprint to store the list of missing dependencies without immediately
emitting an error, and ModuleContext.GetMissingDependencies to return
the missing dependencies to the primary builder.  If the primary builder
does not call ModuleContext.GetMissingDependencies Blueprint will emit
dependency errors.
2 files changed
tree: 959fd176f2068e9ce4f1a91c87aa72846711fade
  1. bootstrap/
  2. bpfmt/
  3. bpmodify/
  4. choosestage/
  5. deptools/
  6. gotestmain/
  7. gotestrunner/
  8. loadplugins/
  9. parser/
  10. pathtools/
  11. proptools/
  12. tests/
  13. .gitignore
  14. .travis.fix-fork.sh
  15. .travis.install-ninja.sh
  16. .travis.yml
  17. Blueprints
  18. bootstrap.bash
  19. build.ninja.in
  20. context.go
  21. context_test.go
  22. context_test_Blueprints
  23. CONTRIBUTING.md
  24. doc.go
  25. LICENSE
  26. live_tracker.go
  27. mangle.go
  28. module_ctx.go
  29. ninja_defs.go
  30. ninja_strings.go
  31. ninja_strings_test.go
  32. ninja_writer.go
  33. ninja_writer_test.go
  34. package_ctx.go
  35. README.md
  36. scope.go
  37. singleton_ctx.go
  38. splice_modules_test.go
  39. unpack.go
  40. unpack_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.