Gitiles
Code Review Sign In
review.blissroms.org / platform_build_blueprint / b89d91c67ccfefc8ff0293dbe1fa931c491137c1
commitb89d91c67ccfefc8ff0293dbe1fa931c491137c1[log] [tgz]
authorColin Cross <ccross@android.com>Fri Jan 17 16:52:47 2020 -0800
committerColin Cross <ccross@android.com>Tue Jan 21 11:49:27 2020 -0800
tree48f93341777e932fd5ef45161b0f3b5ddae6a8ef
parent6ea3f9ddd2fc8ec9815c8e4c7095bff91f0714c8 [diff]
Make FilterPropertyStructSharded smarter

FilterPropertyStructSharded was just sharding the top level
properties into groups of 10.  For nested property structs
this can be insufficient - there could be a single top level
property with many properties below it.

Take a maximum name size, and track the size used by parent
structs to determine when sharding a nested struct is necessary.

Bug: 146234651
Test: filter_test.go
Change-Id: I5b5ed11ea27a0325b2fd6c2c3fb427ea1e2af0c2
2 files changed
tree: 48f93341777e932fd5ef45161b0f3b5ddae6a8ef
  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. glob_test.go
  28. go.mod
  29. LICENSE
  30. live_tracker.go
  31. mangle.go
  32. module_ctx.go
  33. module_ctx_test.go
  34. name_interface.go
  35. ninja_defs.go
  36. ninja_strings.go
  37. ninja_strings_test.go
  38. ninja_writer.go
  39. ninja_writer_test.go
  40. package_ctx.go
  41. README.md
  42. scope.go
  43. singleton_ctx.go
  44. splice_modules_test.go
  45. 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.