How do I include C binaries in a kotlin multiplatform library? Currently the app that consumes the l...

# multiplatform

[jQrgen]

How do I include C binaries in a kotlin multiplatform library? Currently the app that consumes the library all needs these as co-dependencies

[François]

https://kotlinlang.org/docs/multiplatform-add-dependencies.html

[François]

I guess, it's. Oh, for a library, you need to copy them in your framework bundle

[jQrgen]

Hey again @François, doesn't say anything about where to put .so files etc there 🙂

[jQrgen]

What is the framework bundle? Will that work for all targets?

[François]

You need to do it manually, but it depends on what kind of framework you're using

[François]

are you building a xcframework?

[jQrgen]

I think so. How can I check?

[jQrgen]

https://gitlab.com/nexa/libnexakotlin

[jQrgen]

We need Android, iOS and JVM targets. The other targets are kind of just hanging in there

[François]

Adding dynamic libs for a library targeting iOS is a bit tricky.

[François]

First, you need to link your library to your library.
For exemple:

val defFilRootPath = "iosDeps"
    val frameworkRootPath = "$projectDir/iosDeps/Carthage/Build"
    val armSimArch = "ios-arm64_x86_64-simulator"
    val armDevArch = "ios-arm64"
 iosSimulatorArm64 {
        compilations.getByName("main") {
            val KeePassKit by cinterops.creating {
                // Path to .def file
                defFile("$defFilRootPath/KeePassKit.def")
                compilerOpts("-framework", "KeePassKit", "-F$frameworkRootPath/KeePassKit.xcframework/$armSimArch")
                extraOpts += listOf("-compiler-option", "-fmodules")
            }
            val KissXML by cinterops.creating {
                defFile("$defFilRootPath/KissXML.def")
                compilerOpts("-framework", "KissXML", "-F$frameworkRootPath/KissXML.xcframework/$armSimArch")
                extraOpts += listOf("-compiler-option", "-fmodules")
            }
        }

        binaries.all {
            // Tell the linker where the framework is located.
            linkerOpts(
                "-ObjC",
                "-framework",
                "KeePassKit",
                "-F$frameworkRootPath/KeePassKit.xcframework/$armSimArch",
                "-framework",
                "KissXML",
                "-F$frameworkRootPath/KissXML.xcframework/$armSimArch",
            )
        }
    }

[François]

the understanding of compilerOpts is crucial

[François]

But as you're not using xcframework the format is different.

[François]

That's why CocoaPods is easier for integrate different kind of iOS library.

[jQrgen]

How can you see that we are not using xcframework? What are we using then? 🙂

[François]

An XCFramework bundle, or artifact, is a binary package created by Xcode that includes the frameworks and libraries necessary to build for multiple platforms (iOS, macOS, visionOS, tvOS, watchOS, and DriverKit), including Simulator builds. The frameworks can be static or dynamic and also include headers.

Include an XCFramework bundle inside a Swift package to distribute code in binary form for use in other projects. For more information, see Distributing binary frameworks as Swift packages.

<https://developer.apple.com/documentation/xcode/creating-a-multi-platform-binary-framework-bundle>

[François]

Basically, a xcframework is a folder containing subfolder for each targeting Apple platform

[François]

It's a standard on iOS...

[François]

For what you show, you're using the old format.

[jQrgen]

Is it hard to upgrade to the new format?

[jQrgen]

Where should the dynamic libraries be placed to be included in the Android and JVM targets?

[François]

Did you already link/compile them to your library?

[jQrgen]

Checking...

[François]

if the subject of your issue is just about placing, it will depend on your project configuration, it could be complex.