#KLIB LIBRARY ANDROID#

Sorry for a long and complicated answer, please contact me with any questions in the comment section below.

Use shared or static library compiled from Kotlin/Native easier than using C/C++ native library( sorry, but it will be the same JNI thing you probably try to avoid here).

Publish bindings and do not care about linking the resulting artifact with the C library.

androidApp project in general or androidMain source set in shared)

Depend on a KLIB from the Kotlin/JVM modules(e.g.

#KLIB LIBRARY ANDROID#

Delete the Kotlin/Native Android target, and code without C API usage at the shared/src/androidMain/kotlin/.Use this shared library as described in the Android NDK documentation( here).Compile the code using those bindings to a shared library(. Over a decade ago, k:lib (formerly Kwench) brought a paradigm shift to the concept of conventional corporate libraries by enabling companies to provide their employees access to thousands of books across 40+ categories without the hassles of administration effort and savings on space, people, process and technology costs.Use bindings from your Kotlin/Native code(add files to shared/src/androidNativeArm64Main/kotlin/).Here are the things you can do, and cannot do in the current state of the project: Can 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.

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.

Klib library