Google Git
Sign in
android / platform / build / blueprint / 84f1ca233368f29bf12be899ab42ec79759dd0c0
commit84f1ca233368f29bf12be899ab42ec79759dd0c0[log] [tgz]
authorDan Willemsen <dwillemsen@google.com>Mon Dec 19 19:30:49 2016 -0800
committerDan Willemsen <dwillemsen@google.com>Tue Dec 20 04:08:50 2016 +0000
tree77f60aaf20b58bc0555861c6fedeac4504cc7ac8
parenta00e3744ddc571eb03c3d131566addf87f053e1f [diff]
parentb431941604410f2bab7101d87e79701fba9c0407 [diff]
Merge branch 'aosp/upstream' into master

* aosp/upstream:
  Prevent glob from accessing hidden files

Bug: 33672964
Bug: 32676828
Bug: 33744259
Test: Soong's build.ninja files are the same before/after
Test: Doesn't crash on bad .git symlinks anymore
Change-Id: Ib11953092e270101c9f9b6f2961d22660f99b979
tree: 77f60aaf20b58bc0555861c6fedeac4504cc7ac8
  1. bootstrap/
  2. bpfmt/
  3. bpmodify/
  4. deptools/
  5. gotestmain/
  6. gotestrunner/
  7. loadplugins/
  8. parser/
  9. pathtools/
  10. proptools/
  11. tests/
  12. .gitignore
  13. .travis.fix-fork.sh
  14. .travis.gofmt.sh
  15. .travis.install-ninja.sh
  16. .travis.yml
  17. blueprint.bash
  18. Blueprints
  19. bootstrap.bash
  20. build.ninja.in
  21. context.go
  22. context_test.go
  23. CONTRIBUTING.md
  24. doc.go
  25. fs.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.