As you don't have such a source set at this moment, your project cannot build correctly, and shows warning about missing actual declaration.Ĭoncluding everything described above. It provides you an ability to use mylibs API from Kotlin code, written in the androidNativeArm64Main source set. KLIB, which you created here, is not a library itself, but a set of bindings for the native library( mylib). Those bindings are applicable only as a part of the Kotlin/Native compilation.You're able to define a cinterop block, creating bindings for the header, but.It uses the other compiler, and produces a shared library as a result.
#Kotlin klib android
The androidNativeArm64, this is a Kotlin/Native target, not a classic Android one. In your code, I see an additional platform declaration. This is important because this project is built with Kotlin/Native and Kotlin/JVM. The important detail here is that KMM aims to make it easier for developers to include this shared code into their existing codebase - usually Swift or Objective-C for iOS and Java or Kotlin/JVM for Android. KMM technology is about sharing your code between two different platforms, iOS and Android. Kotlin Multiplatform in general consists of three different compilers: one to build for the JVM, one to transpile to the JS, and one to compile platform-specific native binaries(executables, static or shared libraries). Please check out the documentation for details, while I'll try to explain the basic concept here. You are probably confused about different Kotlin versions aiming for a different platform.
0 kommentar(er)
