Google Git
Sign in
fuchsia / third_party / blueprint / 4d6af1f89e0c434aa0cc42e0d061548d2ddf7cfa
commit4d6af1f89e0c434aa0cc42e0d061548d2ddf7cfa[log] [tgz]
authorDan Willemsen <dwillemsen@google.com>Fri Sep 11 16:55:53 2015 -0700
committerDan Willemsen <dwillemsen@google.com>Mon Sep 14 13:39:34 2015 -0700
treeeb612e90fa805dcad2657f747f1e5f7e02dbd6cb
parent9cdb70b93bcbb6e1e1575537546cb7f2cc6a4641 [diff]
Fix bootstrap and separate buildDir ninja cleanup

With the introduction of $buildDir in bootstrapDir, the ninja cleanup
step hasn't been able to cleanup during the bootstrap stages. The main
stage was unaffected, as long as you were using "." as your buildDir.

Change-Id: I277dd7864989f9052d96cab9ce377548a1391a80
2 files changed
tree: eb612e90fa805dcad2657f747f1e5f7e02dbd6cb
  1. bootstrap/
  2. bpfmt/
  3. bpmodify/
  4. choosestage/
  5. deptools/
  6. gotestmain/
  7. parser/
  8. pathtools/
  9. proptools/
  10. tests/
  11. .gitignore
  12. .travis.fix-fork.sh
  13. .travis.install-ninja.sh
  14. .travis.yml
  15. Blueprints
  16. bootstrap.bash
  17. build.ninja.in
  18. context.go
  19. context_test.go
  20. CONTRIBUTING.md
  21. doc.go
  22. LICENSE
  23. live_tracker.go
  24. mangle.go
  25. module_ctx.go
  26. ninja_defs.go
  27. ninja_strings.go
  28. ninja_strings_test.go
  29. ninja_writer.go
  30. ninja_writer_test.go
  31. package_ctx.go
  32. README.md
  33. scope.go
  34. singleton_ctx.go
  35. splice_modules_test.go
  36. unpack.go
  37. 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.