You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
rules_kotlin currently deploys a sandwich library to allow for Kotlin + android resources compilation which is bit of an atypical setup that involves exporting as well. Since our own kt_db_android_library is able to use stubs to compile Kotlin classes successfully with small bit of work we could use it for non databinding modules as well. The new approach might also allow us to compile actual resources processing from android_library and our stub R class + kt_jvm_library in parallel.
We might only see proper benefits if we implement #5 worker support but worth a try.
The text was updated successfully, but these errors were encountered:
arunkumar9t2
changed the title
Explore if non databinding modules can also use the stub compiler approach by generating R class alone.
Explore if non databinding modules can also use the stub compiler approach
Jul 30, 2022
rules_kotlin
currently deploys a sandwich library to allow for Kotlin + android resources compilation which is bit of an atypical setup that involves exporting as well. Since our ownkt_db_android_library
is able to use stubs to compile Kotlin classes successfully with small bit of work we could use it for non databinding modules as well. The new approach might also allow us to compile actual resources processing fromandroid_library
and ourstub R class + kt_jvm_library
in parallel.We might only see proper benefits if we implement #5 worker support but worth a try.
The text was updated successfully, but these errors were encountered: