New issue
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
couldn't find "libj2v8_android_armv7l.so" #70
Comments
On android you need to specify where to unpack the native libraries. We do something like this: |
Oh, so it will drop the native libs there on runtime? Or is that the directory that the native runtimes need to be living already? Update: Throws the same error. Do I need to put something in the dataDir for the lib to find? |
Oh, I should mention that I'm using Android Studio. It seems as though this is the key:
I've tried creating my own jniLibs directory with the armeabi, armeabi-v7a, and x86 directories, placing the appropriate .so files in each. No go. |
It will unpack them there. They are in the jar. If you don't specify it
|
Well, this is interesting. I created a jniLibs folder and put the libj2v8_android_armv7l.so in the armeabi-v7a directory. That got passed the error. However, your example here fails:
Throwing this:
looks like valid JS to me. It's closer though. I think for Android Studio you'll have to bundle the .jar a little differently so that the .so ends up in the correct directory. That's my guess. |
Sorry, I was trying to answer you from my phone without looking at the code. Ok, two things.
This works fine:
|
I have the same error
|
Can you try with Version 3.1.0 (just pushed it to maven central 1 hour ago). This packages the androd libs an aar, which should make loading native bits much easier.
The gradle dependency is as follows:
|
Closing. Please re-open if this problem persists. |
I wanted to check out the performance of your lib in a native Android app.
I've used both:
compile 'com.eclipsesource.j2v8:j2v8_android_armv7l:2.2.1'
and placing the .jar directly into my libs folder in Android studio.
In each case, I am getting this error:
The text was updated successfully, but these errors were encountered: