Gitiles
Code Review Sign In
review.blissroms.org / platform_build_blueprint / 3c8c3346d2c3eef85ce99ab58bd8aa07a53d6bc1
commit3c8c3346d2c3eef85ce99ab58bd8aa07a53d6bc1[log] [tgz]
authorJeff Gaston <jeffrygaston@google.com>Thu Nov 30 17:30:42 2017 -0800
committerJeff Gaston <jeffrygaston@google.com>Mon Dec 04 17:16:21 2017 -0800
tree6a5cc9e05c3fc17a476e90e536bff4633d89bffa
parent656870fbca9e8d8d7884848a0f8d8c57a27fc87b [diff]
Pass ModulePath to NameInterface

To allow it to validate that the filename equals Android.bp

Bug: 65683273
Test: m -j nothing # which runs tests
Change-Id: I171dddd102590df558053b615d39c75c00b6ac6e
3 files changed
tree: 6a5cc9e05c3fc17a476e90e536bff4633d89bffa
  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. name_interface.go
  32. ninja_defs.go
  33. ninja_strings.go
  34. ninja_strings_test.go
  35. ninja_writer.go
  36. ninja_writer_test.go
  37. package_ctx.go
  38. README.md
  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.