Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Explore if non databinding modules can also use the stub compiler approach #36

Open
arunkumar9t2 opened this issue Jul 30, 2022 · 0 comments
Labels
enhancement New feature or request

Comments

@arunkumar9t2
Copy link
Contributor

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.

@arunkumar9t2 arunkumar9t2 added the enhancement New feature or request label Jul 30, 2022
@arunkumar9t2 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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant