You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, I'm currently hitting this error when trying to build my Android app (for an arm64 emulator) on macOS:
Cause: multik-openblas-jvm-0.2.3 extracted from path ~/.gradle/caches/8.9/transforms/4d3515c442b573850b7bc131f7841f9c/transformed/multik-openblas-jvm-0.2.3/linuxX64/libmultik_jni-linuxX64.so is not an ABI
That file exists (as does the libmultik_jni-androidArm64.so version it seems is actually relevant) but I'm not building on Linux nor do I define linuxX64 anywhere in my config.
I can build and run my commonTest test cases which indirectly depend upon multik-core and multik-default.
It works until I delete ~/.gradle so I probably won't hit it myself for a while (or until I update to the next multik release). But I'd really like a durable solution if possible.
Actually, I have to delete the file any time I invalidate build caches and will probably happen every time I upgrade multik so it is a little more of a problem than I asserted above.
After discussion on Slack, it seems the best option for me for now is to just use multik-kotlin as the build for openblas complicates the packaging (and dependency management) for Android and I don't strictly need the highest performance.
This issue still seems valid though so I'll leave it open.
Hi, I'm currently hitting this error when trying to build my Android app (for an arm64 emulator) on macOS:
That file exists (as does the
libmultik_jni-androidArm64.so
version it seems is actually relevant) but I'm not building on Linux nor do I definelinuxX64
anywhere in my config.I can build and run my
commonTest
test cases which indirectly depend uponmultik-core
andmultik-default
.I've got the following in my
build.gradle.kts
:Do I have a mistake in my
build.gradle.kts
? Can I / do I need to somehow explicitly excludelinuxX64
or that.so
file?Thanks!
The text was updated successfully, but these errors were encountered: