What does the `-include-binary` KN compiler arg ac...

# kotlin-native

[Adam S]

What does the -include-binary KN compiler arg actually do? Does it just tell the compiler to package the files into the my-lib.klib in the /my-lib/default/targets/${targetName}/included/ dir?

Context: I have two .a static library files ( 'debug' and 'release'). I can't see how my subproject my-app can only use the debug my-lib when running runMyAppDebugExecutableMacosArm64 and the release my-lib when running runMyAppReleaseExecutableMacosArm64.

I was thinking about making two variants of my library, one that produces a my-lib-release.klib and another that produces my-lib-debug.klib. The only difference being the included static libs. If I can build the .klib manually, and just update the included files, that'd be a solution (albeit complicated and something I'd prefer to avoid).

[ephemient]

I don't know of a good solution to this, especially with https://youtrack.jetbrains.com/issue/KT-70946/Native-mark-bundling-static-libs-to-klibs-experimental

[Adam S]

interesting, thanks!

[Adam S]

I guess bundling static libs is an usual feature for a compiler. Supporting sharing static libs from the build tooling side makes more sense, it's just a pain the in arse.