Big Chungus06/04/2022, 4:32 PM
category includes both, java-jvm and android-jvm
russhwolf06/04/2022, 6:28 PM
Big Chungus06/04/2022, 6:32 PM
russhwolf06/04/2022, 6:35 PM
Big Chungus06/04/2022, 6:35 PM
russhwolf06/04/2022, 6:37 PM
Big Chungus06/04/2022, 6:37 PM
Landry Norris06/04/2022, 7:01 PM
I can understand why most libraries don’t support android NDK, but there are cases where I need the NDK, and it’s a bit frustrating not having much support.
val androidTargets = listOf(androidNativeArm32(), androidNativeArm64(), androidNativeX86(), androidNativeX64())
Big Chungus06/04/2022, 7:04 PM
russhwolf06/04/2022, 7:08 PM
Big Chungus06/04/2022, 7:09 PM
Landry Norris06/04/2022, 7:09 PM
Big Chungus06/04/2022, 7:11 PM
russhwolf06/04/2022, 7:13 PM
Landry Norris06/04/2022, 7:13 PM
Big Chungus06/06/2022, 8:14 PM
category/family counts - they all seem to be js artefacts without
gradle metadata attribute for some reason. Is it safe to assume
backend for them? @bashor are you able to provide some details of why that might be the case? I've checked a few of them and they're mainly published between 2019 and 2020.
bashor06/07/2022, 3:05 PM
Is it safe to assumeYes.backend for them?
@bashor are you able to provide some details of why that might be the case? I’ve checked a few of them and they’re mainly published between 2019 and 2020.Before we start publishing separate artifacts for K/JS IR and non-IR there was no need for an attribute to distinguish them. (cc @Ilya Goncharov [JB])
to avoid confusing with future K/Wasm artifacts
Big Chungus06/07/2022, 3:09 PM
Ilya Goncharov [JB]06/07/2022, 3:13 PM
value in gradle metadata
bashor06/07/2022, 3:29 PM
Big Chungus06/10/2022, 1:21 PM
bashor06/10/2022, 1:54 PM
Big Chungus06/10/2022, 3:14 PM
bashor06/10/2022, 3:43 PM
Big Chungus06/10/2022, 3:45 PM
svyatoslav.scherbina06/10/2022, 4:22 PM
One more question. kotlin-test metadata has akotlin-test for Kotlin/Native is bundled with the compiler. The same klib is used for all Kotlin/Native targets. The kotlin-test library in Maven Central doesn’t in fact contain any code for Kotlin/Native, to the best of might knowledge.platform variant without
nativeattribute. Can that be understood that the same variant should be used for ALL native targets?
bashor06/10/2022, 4:36 PM
Big Chungus06/10/2022, 4:46 PM
svyatoslav.scherbina06/10/2022, 4:55 PM
Can any other project using KGP produce metadata without target attribute for native variants (assuming no manual user interaction)Sorry, I don’t get your question. What exactly should KGP produce in this case, and how it should be consumed? Metadata describes only API, but not implementation.
Big Chungus06/10/2022, 5:02 PM
So I have two questions: 1. Can thehas a
nativeApiVariantattribute. However, unlike all the other KMP libs with native targets, it does not declare
attribute be missing in a third-party lib that uses KGP plugin to produce gradle metadata and has native targets? 2. Can the abscence of
attribute be understood as "this lib supports all K/N targets"?
svyatoslav.scherbina06/10/2022, 5:27 PM
1. Can theI guess it can. For example, like this: https://github.com/JetBrains/kotlin/blob/fb9c5c13bd9e37b775648550437fe8264687839f/libraries/kotlin.test/build.gradle.kts#L77attribute be missing in a third-party lib that uses KGP plugin to produce gradle metadata and has native targets?
2. Can the abscence ofUnless someone explicitly modified the klib contents manually, a single klib (produced by KGP) can’t support multiple Kotlin/Native targets. So, if such a variant exists in Gradle metadata for a library, it probably doesn’t have any files, so (this variant) doesn’t actually provide any API. (If it does have files, then see above — the klibs are probably modified manually; it might be necessary to look into klib to find whether it contains any real code or not).attribute be understood as “this lib supports all K/N targets”?
Big Chungus06/10/2022, 5:31 PM