it's interesting pulling in dependencies using gra...
# multiplatform
k
it's interesting pulling in dependencies using gradle metadata - sometimes I only need a common dependency, and sometimes that doesn't work
i wonder what ends up being the difference
atomicfu seems to work, while kotlinx-serialization-runtime doesn't
r
It depends on how they've been published. A bunch of the Jetbrains libs actually have
xxx-native
publications that you can use just from common to hit all platforms. Unintuitive naming though.
k
oh, you refer to native from common?
in theory you're supposed to be able to just refer to the artifact name proper, without any extension
r
I think they left the bare artifact as jvm in some cases for back-compatibility, but I don't know the whole story there
But that's how serialization and coroutines seem to work at least
k
let me give that a try. i did notice that jvm/android refers to the bare artifact name
confirmed the native variants work for all kotlinx packages
now if I could just figure out why suparnatural-fs isn't work right