We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I spent a couple days getting an Android build working: https://gitlab.com/dkml/ext/dkml-jnr#dkml-jnr.
But I ran into a major showstopper ... JNR uses dynamic bytecode classloading:
jnr-ffi/src/main/java/jnr/ffi/provider/jffi/AsmClassLoader.java
Lines 24 to 40 in 0deaac0
Android does not allow bytecode classloading: https://developer.android.com/training/articles/perf-jni.html#unsupported-featuresbackwards-compatibility
Even when I use System.setProperty("jnr.ffi.asm.enabled", "false"); the AsmClassLoader is still used in:
System.setProperty("jnr.ffi.asm.enabled", "false");
jnr-ffi/src/main/java/jnr/ffi/provider/jffi/ReflectionLibraryLoader.java
Lines 105 to 108 in 0deaac0
Anyway, I'm going to switch to JNI. If someone wants to continue the ball rolling, they can.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
I spent a couple days getting an Android build working: https://gitlab.com/dkml/ext/dkml-jnr#dkml-jnr.
But I ran into a major showstopper ... JNR uses dynamic bytecode classloading:
jnr-ffi/src/main/java/jnr/ffi/provider/jffi/AsmClassLoader.java
Lines 24 to 40 in 0deaac0
Android does not allow bytecode classloading: https://developer.android.com/training/articles/perf-jni.html#unsupported-featuresbackwards-compatibility
Even when I use
System.setProperty("jnr.ffi.asm.enabled", "false");
the AsmClassLoader is still used in:jnr-ffi/src/main/java/jnr/ffi/provider/jffi/ReflectionLibraryLoader.java
Lines 105 to 108 in 0deaac0
Anyway, I'm going to switch to JNI. If someone wants to continue the ball rolling, they can.
The text was updated successfully, but these errors were encountered: