Support androidNative target

[Syrou]

Been trying to setup coroutines against

  fromPreset(presets.androidNativeArm64, 'androidNative')

but it seems not to work with

 implementation "org.jetbrains.kotlinx:kotlinx-coroutines-core-native:$coroutines_version"

but it does not resolve the dependencies, is this not working yet?

[SeekDaSky]

The gradle file for K/N compilation does not have android native in its targets so you can not use it in K/N android projects. But you could maybe try to clone the repo, add the target and see if it compiles, but that is a bit experimental.

Edit: that won't work, AtomicFU does not have the android native target either

[Syrou]

@SeekDaSky Seems like you are correct, there is support for it in kotlin multiplatform but these libraries are still missing it. I'm hoping for it to get added soon.

[elizarov]

What would be your use-case of using coroutines with androidNative target?

[Syrou]

@elizarov In this specific case it would be to standardize a communication bridge with Unity. iOS makes use extern "C" in order for unity to be able to run iOS code. My wish in this specific case would to open up the same possibility for android and reuse the exact same code in Unity for both platforms

but I also see a great possibility to write Native Libraries and hopefully make it more hard for people to reverse them since it would no longer be java code (This is still true with the common base, but it would take it all the way)

[dhakehurst]

+1

[elizarov]

@dhakehurst Can you, please, elaborate a bit on what is your use-case for it?

[dhakehurst]

I would have thought obvious. ?
Kotlin 1.4 provides androidNative as a target.
I want to build androidNative applications?

Maybe something i miss understand about this target.

[LouisCAD]

@dhakehurst Why do you need to run with the NDK and not in ART as most apps do?

[dhakehurst]

Well, I don't "need" to. I want to.
it is a valid kotlin Target, so why not support it?
is it a problem to support it?

[dhakehurst]

there are many articles discussing ART vs NDK.
e.g. https://www.androidauthority.com/java-vs-c-app-performance-689081/

which states
"Google recommends using the NDK for “CPU-intensive applications such as game engines, signal processing, and physics simulations.”"