A modern programming language that makes developers happier.

kotlinlang

Hello everyone!
As some of you might know, in <https://blog.jetbrains.com/kotlin/2020/03/kotlin-1-3-70-released/#kotlin-native|1.3.70> we added support for compiler caches for `macosX64` and `iosX64` targets. Long story short, compiler caches make compilation time of debug builds (e.g. `linkDebug...`) in Gradle significantly faster (well, except the first one, when dependencies are caching and Gradle daemon is warming up).
In <https://github.com/JetBrains/kotlin/releases/tag/v1.5.0-M1|1.5.0-M1> we add opt-in support for compiler caches for two more targets:
•  `iosArm64`
•  `linuxX64` (only on Linux host)
To enable them add a single line to your `gradle.properties`.
For `linuxX64` target:
```kotlin.native.cacheKind.linuxX64=static```
For `iosArm64` target:
```kotlin.native.cacheKind.iosArm64=static```
"Why not enable it by default?" you might ask. While it doesn't break our test projects, it might break yours.
And who likes broken compilation after compiler update? :)
So, we asking you to test compiler caches on your projects and <https://kotl.in/issue|report> to us if you encounter any kind of problems. Let's make Kotlin faster together!

Why are the Linux ARM targets not covered for the compiler caches?

If we support everything in one release, we will have no features for the next releases!

Jokes aside, nothing prevents us from adding caches for these targets in the future. But every feature requires engineering resources for implementation and testing, and these resources are not infinite :)

Sorry to revive a dead thread, but could anyone confirm if `kotlin.native.cacheKind=none` disables cinterop caching too?