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

Manage Kotlin native cache kind automatically based on Kotlin version #3477

Merged
merged 6 commits into from
Aug 11, 2023

Conversation

AlexeyTsvetkov
Copy link
Collaborator

No description provided.

Copy link
Contributor

@dima-avdeev-jb dima-avdeev-jb left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@AlexeyTsvetkov AlexeyTsvetkov merged commit 950d5a9 into master Aug 11, 2023
3 checks passed
@AlexeyTsvetkov AlexeyTsvetkov deleted the kotlin-native-caching-settings branch August 11, 2023 15:33
@igordmn
Copy link
Collaborator

igordmn commented Aug 11, 2023

Checked removing kotlin.native.cacheKind=none on 1.5.0-dev1147 and Kotlin 1.9.0 - it works 🎉

AlexeyTsvetkov added a commit to AlexeyTsvetkov/compose-jb that referenced this pull request Aug 16, 2023
We tried to enable the compiler cache, when
Kotlin/Native 1.9.0 is used.
Prior to Kotlin 1.9.0, the caching could not
be used with Compose, because code generation would fail.
With Kotlin 1.9.0, code generation succeeds, but  generated debug symbols cause issues with dsymutil during xcode build.
For more details, see https://youtrack.jetbrains.com/issue/KT-61270

This change partially reverts JetBrains#3477 and JetBrains#3496

Now, we always set `kotlin.native.cacheKind=none` in
Compose Multiplatform Gradle plugin for all
versions of Kotlin until KT-61270 is fixed.
Also, explicit cache kind error becomes a warning again.
AlexeyTsvetkov added a commit that referenced this pull request Aug 16, 2023
We tried to enable the compiler cache, when
Kotlin/Native 1.9.0 is used.
Prior to Kotlin 1.9.0, the caching could not
be used with Compose, because code generation would fail.
With Kotlin 1.9.0, code generation succeeds, but  generated debug symbols cause issues with dsymutil during xcode build.
For more details, see https://youtrack.jetbrains.com/issue/KT-61270

This change partially reverts #3477 and #3496

Now, we always set `kotlin.native.cacheKind=none` in
Compose Multiplatform Gradle plugin for all
versions of Kotlin until KT-61270 is fixed.
Also, explicit cache kind error becomes a warning again.
igordmn pushed a commit that referenced this pull request Aug 16, 2023
We tried to enable the compiler cache, when
Kotlin/Native 1.9.0 is used.
Prior to Kotlin 1.9.0, the caching could not
be used with Compose, because code generation would fail.
With Kotlin 1.9.0, code generation succeeds, but  generated debug symbols cause issues with dsymutil during xcode build.
For more details, see https://youtrack.jetbrains.com/issue/KT-61270

This change partially reverts #3477 and #3496

Now, we always set `kotlin.native.cacheKind=none` in
Compose Multiplatform Gradle plugin for all
versions of Kotlin until KT-61270 is fixed.
Also, explicit cache kind error becomes a warning again.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants