what's the most straightforward way to add a .klib...

# kotlin-native

[Kris Wong]

what's the most straightforward way to add a .klib artifact to the maven publication created for an iOS target with a framework binary?

[kpgalligan]

Curious about your setup. What does the config look like

[Kris Wong]

quite simple

[Kris Wong]

iosX64("ios") {
        binaries {
            framework()
        }
    }

[Kris Wong]

maven-publish is applied

[Kris Wong]

the only artifact that is publishes is a sources.jar

[Kris Wong]

i've been messing around with it for a couple hours and can't seem to find any way to connect the dots on this

[kpgalligan]

I would think you’d need to also add the library binary alongside the framework

[kpgalligan]

Not 100% sure how to do it off hand, but here are the constant options

[kpgalligan]

message has been deleted

[kpgalligan]

Probably somewhere in this neighborhood: https://github.com/JetBrains/kotlin/blob/f47aafc47163407f99cfc27fbd1ac52a47392454/libraries/tools/kotlin-gradle-plugin/src/main/kotlin/org/jetbrains/kotlin/gradle/dsl/AbstractKotlinNativeBinaryContainer.kt#L256

[Kris Wong]

i tried both staticLib and dynamicLib, which create .a and .dylib, respectively

[kpgalligan]

Hmm. If you just remove framework() does it deploy correctly?

[Kris Wong]

i see there is a .klib output kind, but didn't see an easy way to link that to an executable

[Kris Wong]

no

[Kris Wong]

i also tried passing the iosMainKlibrary task to artifact, but it's not the right type

[Kris Wong]

i don't want to just hardcode the path to the .klib in the build directory because that could break on any plugin change

[Kris Wong]

you would figure this would be pretty simple =/

[kpgalligan]

If you just have iosX64("ios") without a binary specified, and you’re not publishing with that, then I think you have a different config issue.

[kpgalligan]

I would work on it from that direction. Get the library publishing, then add the framework back

[kpgalligan]

Not the easiest example to follow, but from my firebase lib: https://github.com/touchlab/FirestoreKMP/blob/master/firestore/build.gradle#L77

[kpgalligan]

kotlin {

    android {
        publishAllLibraryVariants()
    }

    iosArm64()
    iosX64()
...

[Kris Wong]

iosX64("ios") {
//        binaries {
//            framework()
//        }
        mavenPublication {
            artifactId = "iosx64"
            artifacts.all { println(file) }
        }
    }

[Kris Wong]

prints /Users/krisw/Dev/act/TelemetryModule/build/libs/TelemetryModule-ios-0.1-sources.jar

[kpgalligan]

I would start with one of the several examples of libraries that publish and work from there. I can’t debug your gradle publishing config, but once it’s set up it does work. You need to get that working before also trying to add framework() or you’ll have a lot of concurrent issues

[kpgalligan]

Firestore includes a publish gradle file https://github.com/touchlab/FirestoreKMP/blob/master/firestore/build.gradle#L163

[Kris Wong]

yeah I looked at stately and didn't see anything obvious I was missing

[kpgalligan]

I’ve been mostly copy/pasting that around

[kpgalligan]

Also check that enableFeaturePreview('GRADLE_METADATA') is in settings.gradle. It’s the first thing I check now because I forgot it so many times

[Kris Wong]

yeah i've got that

[Kris Wong]

the metadata artifact and android artifacts work

[Kris Wong]

oh my lord i've been totally wasting my time. it publishes the artifacts, but artifacts.all doesn't include them for some reason so they weren't being printed

[kpgalligan]

Ah

[Kris Wong]

🤦

[kpgalligan]

I’m not a big fan of gradle publish config

[Kris Wong]

do you know are both

"kotlinMultiplatform", "metadata"

required to publish a multiplatform library?

[kpgalligan]

No idea

[kpgalligan]

I just publish the stuff and it works out

[Kris Wong]

aight. no reason not to include them both.

[Kris Wong]

thank you as always

[russhwolf]

I don’t have a great handle on the difference between them, but can confirm that both kotlinMultiplatform and metadata are required. Was messing around some with what does and doesn’t need to be included when I was setting up CI for Multiplatform Settings

[Kris Wong]

yeah, the multiplatform artifact allows you to specify "groupprojectversion" w/o having to specify each platform

[Kris Wong]

it just tells gradle about the metadata artifact

[Kris Wong]

<!-- This module was also published with a richer model, Gradle metadata,  -->
  <!-- which should be used instead. Do not delete the following line which  -->
  <!-- is to indicate to Gradle or any Gradle module metadata file consumer  -->
  <!-- that they should prefer consuming it instead. -->
  <!-- do_not_remove: published-with-gradle-metadata -->

[Kris Wong]

magic comment

[russhwolf]

Nice. Where’s that comment live?

[Kris Wong]

in the multiplatform POM

[russhwolf]

Ah I see it. Thanks!

[Kris Wong]

np