As kotlin-native evolves especially with 1.4 it wo...

# kotlin-native

[katokay]

As kotlin-native evolves especially with 1.4 it would be really great if Jetbrains can help clarify package publishing that include native dependencies. For reference, this discussion shows it's not real clear at the moment or what the vision is.

https://github.com/GitLiveApp/firebase-kotlin-sdk/issues/36#issuecomment-643244227

[napperley]

I'm assuming you are only talking about the mobile platforms. Package publishing will be different for the other platforms like Linux (targets like linuxX64, linuxArm32Hfp, linuxArm64 etc) for example.

[katokay]

That's my specific pain point yes, but the problem will exist there as well. Yes, of course it will be different for other platforms and likely for each library. My point is that it's not very clear at the moment and that there's been a lot of change. There are docs that describe specific settings, specific targets. I think what's needed is something that is more narrative. Here we have a library that needs to do this with JS, this with iOS, this with JVM, this for linuxX64. Here's how to publish a package that takes all of this into consideration. Now that we've published our package, users will do this to add a dependency (given their specific use case). Here's how these choices we made earlier affect the end-user adding your package as a dependency.