Has anyone had the issue of using multiple K/N mod...

# kotlin-native

[Andy Gibel]

Has anyone had the issue of using multiple K/N modules and having to combine the Klibs in a single monolithic Framework for iOS consumption? Any gotchas other than just simply exporting the api dependencies?

[Michal Harakal]

One solution we use, is modules “stitching” as described here: https://github.com/JetBrains/kotlin-native/issues/3461#issuecomment-541937515
generally you have another “combined” gradel module, where you reuses source sets from other modules.

[Kris Wong]

i have created an umbrella project and have written a blog post about how I did it. basically just using git submodules and adding the dependencies as subprojects.

[Andy Gibel]

Nice. @Kris Wong got a link handy for that blog? I'd be interesting to take a gander for sure

[Kris Wong]

i'll PM you. it's still a draft until my company publishes it.

[Andy Gibel]

awesome 👍

[spierce7]

git submodules would be a heavy solution that you’d find taxing in the long run. If they had to exist in separate git repos, then using a private maven wagon to release and retrieve prebuilt dependencies would be a much saner approach.

An easier approach though would be to simply just have multiple gradle modules in a single gradle project, which is something that people do with gradle all the time, and kotlin native should handle really well

[Kris Wong]

i don't find submodules to be more or less work than using maven artifacts. however, we're talking iOS frameworks, so there are no maven artifacts

[Kris Wong]

unless you could somehow make that work with the .kilb files directly

[Kris Wong]

alternatively, you could set it up as an Xcode project using CocoaPods

[spierce7]

the multiplatform plugin is able to upload maven artifacts to a specified maven wagon with very little configuration, for all of it’s platforms

[Kris Wong]

i'd like to see an iOS framework that's been uploaded to a maven repo 🙂