I'm trying to figure out why my JVM-only project h...
# gradle
b
I'm trying to figure out why my JVM-only project has a
kotlinNativeBundleConfiguration
in it - anyone have a clue as to where that might be coming from? (obviously without seeing the project it's impossible to say for sure, but I'm looking for ideas)
b
Interesting. Is it unconditionally created - just part of the regular kotlin toolchain?
c
Not sure what exactly this means:
Copy code
if (project.nativeProperties.isToolchainEnabled.get()) {
            addKotlinNativeBundleConfiguration(project)
        }
perhaps there’s something (property gradle.properties???) that is adding in some ‘native’ facet.
blob thinking fast 1
b
the name suggests usage of jvm toolchains, maybe? we do use those.
c
In the context of NativeProperties its the ‘native’ toolchain, not the JVM one. It’s based off of
kotlin.native.toolchain.enabled
property, which defaults to true, suggesting this is always there.
b
ah, interesting! that's a great lead, nice detective work
and thank you
c
np.
b
confirmed! setting it to 'false' makes the native configurations disappear. ...wonder what that will affect. time to go find out!
K 2
a
Could you please file an issue about this to https://kotl.in/issue? cc @Dmitrii Krasnov
d
The
kotlinNativeBundleConfiguration
was presented in KT-49268. Since
2.0.0
we moved downloading Kotlin Native bundle from Gradle configuration phase to execution phase. When you set
kotlin.native.toolchain.enabled=false
you return the old behaviour, which is considered as deprecated and will be removed in future releases.
Oh, you have jvm-only project, sorry. Then as @Alexander.Likhachev said file an issue about this to https://kotl.in/issue