-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Provide a way to selectively disable native targets #3695
Comments
Thanks! Related: #3657 |
To get it right, you have no Compose related code in the commonMain source set, right? |
Correct. I have a module that supports Android, JVM/Desktop, JS and iOS. And I only use Compose in |
Closing this as fixed :) |
Thank you! 🙏 |
… plugin should be applied According to JB Compose team, it is a useful feature requested by their users and a new plugin should also support it. For example: JetBrains/compose-multiplatform#3695 ^KT-67253 Verification Pending
… plugin should be applied According to JB Compose team, it is a useful feature requested by their users and a new plugin should also support it. For example: JetBrains/compose-multiplatform#3695 ^KT-67253 Verification Pending
… plugin should be applied According to JB Compose team, it is a useful feature requested by their users and a new plugin should also support it. For example: JetBrains/compose-multiplatform#3695 ^KT-67253 Verification Pending
… plugin should be applied According to JB Compose team, it is a useful feature requested by their users and a new plugin should also support it. For example: JetBrains/compose-multiplatform#3695 ^KT-67253 Verification Pending
Please check the following ticket on YouTrack for follow-ups to this issue. GitHub issues will be closed in the coming weeks. |
My Gradle module has
org.jetbrains.compose
Gradle plugin applied and the following targets enabled:But I don't need Compose for
ios
andjs
targets. I'm able to disable Compose for Web using the following configuration:However, it looks like there is no API for iOS. Currently I'm using the following workaround, which is not ideal.
The text was updated successfully, but these errors were encountered: