Thread
#multiplatform
    l

    Lars Toft Jacobsen

    1 year ago
    message has been deleted
    l

    Luis

    1 year ago
    It could help if you showed the stacktrace from the error?
    I don’t think you need to specify the
    binaries.framework
    unless you want to customize it (by changing its name for example)
    It would also help if you could you build.gradle, and also tell us which version of kotlin you are using
    l

    Lars Toft Jacobsen

    1 year ago
    Absolutely @Luis, and thanks. Kotlin version is 1.5.21. I cannot share the build gradle unfortunately, but it’s a multi-module project with all things multiplatform being applied in the root build.gradle. I’m trying to build a single sub-project with no dependencies to any of the other projects. Thanks for pointing out that I don’t need the
    binaries.framework
    - I had been playing around with setting the baseName and left it there.
    Error message
    l

    Luis

    1 year ago
    Yeh, sorry @Lars Toft Jacobsen I can’t see what the issue could be without peeking the build.gradle… I do know that on my project I have the iOS declaration depending on a
    SDK_NAME
    variable, so I can build stuff for the iOS simulator
    val iosTarget: (String, KotlinNativeTarget.() -> Unit) -> KotlinNativeTarget = when {
        System.getenv("SDK_NAME")?.startsWith("iphoneos") == true -> ::iosArm64
        else -> ::iosX64
    }
    
    iosTarget("ios") {}
    Maybe you could have an issue with that?
    Also, M1 Arm support was only added in version 1.5.31, but if your debug linking works, I don’t see why that would be an issue…
    l

    Lars Toft Jacobsen

    1 year ago
    Hmm. Ok I gathered as much that the emulator target was my best bet, and it also proved to be the one getting furthest. There's no difference afaics between using the target directly as I do vs setting it via some logic that reads an ENV. I was hoping someone could point to how I could crank out more information from the compiler in order to uncover the actual cause of the linker error or hints as to why the debug linking would succeed when the release one fails.
    Thanks for the input so far @Luis 🙌