I've a bit of confusion with KMP build for native. I'm trying to build for iOS platforms, both sim and device (only 64 bits). So, I've it build as follows:

val ios64 = iosArm64("ios64")
    val iosSim = iosX64("iosSim")
    val iosMain by sourceSets.creating {
        dependencies {
            implementation(kotlin(Config.ios.dependencies.stdlib))
            implementation(Config.ios.dependencies.serialization)
            implementation(Config.ios.dependencies.coroutines)
        }
    }
    val iosTest by sourceSets.creating {
        dependencies {
            implementation(kotlin(Config.ios.dependencies.stdlib))
            implementation(Config.android.dependencies.coroutinesTest)
        }
    }
    configure(listOf(ios64, iosSim)) {
        binaries.framework {
            baseName = Config.ios.frameworkName
            freeCompilerArgs.add("-Xobjc-generics")
        }
        sourceSets {
            @Suppress("UNUSED_VARIABLE")
            val ios64Main by getting {
                dependsOn(iosMain)
            }
            @Suppress("UNUSED_VARIABLE")
            val iosSimMain by getting {
                dependsOn(iosMain)
            }
            @Suppress("UNUSED_VARIABLE")
            val ios64Test by getting {
                dependsOn(iosTest)
            }
            @Suppress("UNUSED_VARIABLE")
            val iosSimTest by getting {
                dependsOn(iosTest)
            }
        }
    }

Now, when I make a publication, it publishes two separate native components for iOS, basically, for both

iossim

, and

ios64

. What's the standard way to do this, such that I can only publish the native library called

native

, and no

iossim

,

ios64

. I feel like I'm missing a link here somewhere... All the sources are in

iosMain

, and

iosTest

folders

do I understand that you want one fat framework?

I have a separate thing in gradle for the fat framework. I'm more about wondering on the maven publication of this library.

what artifact do you intend to publish to maven?

As in what artifacts for ios/native ones?

yes

I'm not entirely sure what I really need, but I wanna be able to use this library as a dependencies in other KMP project for native components. I've

.jar

,

.klib

, and

.pom

that it publishes for

iosSimulator

, and

iosDevice

at the moment

the only way I am familiar with using a native dependency is via subproject, though I get the impression it may be possible with the .klibs. perhaps someone else knows another way.

My initial impression was that, the dependencies manager asks the repo for the correct version of

klib

to download in terms of architecture when we ask

native

, but I'm not sure how I can publish that

i am not familiar with how to publish an MPP to use as a dependency for another MPP, though I do assume that this is working for projects like ktor and others, so you could probably learn from their source repo

I'm looking into those projects, and feel like that's what I'm doing. But I think my basic idea of just publishing the

klib

is wrong in itself. May be I should publish something that is architecture independent, like I do for android, which when used in other KMP project, compiles to

klib

¯\_(ツ)_/¯

Just let the normal KMP publication happen, it publishes everything needed, with Gradle metadata. Then in your client KMP project, you just import the “root” lib and it looks for what it needs. I think the “native” packages you’re talking about are actually “root” packages, there actually are native-ios-arm64 libs etc which gets automagically imported if needed.