Implement worker support for GenerateDataBindingBaseClasses
#16067
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
GenerateDataBindingBaseClasses
toResourceProcessorBusyBox
since Android databinding classes were already a dependency there.ProcessDatabinding
is already part ofResourceProcessorBusyBox
but it was not enabled inpersistent_android_resource_processor
expansion flag. Added that as well.This change is multiplex compatible and probably could use expansion flags as done here #15950.
Results:
In a synthetic generated project with 30 modules here https://github.com/arunkumar9t2/bazel-playground, the worker can be turned off/on with
.bazel.sh build //android/databinding_workers:android_data_binding --strategy=GenerateDataBindingBaseClasses=[sandboxed|worker]
and worker is about 9 to 10% faster.