-
Notifications
You must be signed in to change notification settings - Fork 268
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
Unable to import JNI code ImageUtils #25
Comments
You should post at least the error it gives, not much I can guess from your quick description. I remeber it gave me some headaches when I modified it. Also, remember that everything in the project is compiled into the libpeople_det.so, as for the Android.mk file |
Hey, thanks for your quick reply. Sorry, here is a trace for the error :
Your comments were useful. I am guessing that my project should either have the same package name (which I don't really like) or I should include the project directly rather than relying on the Maven repository? Or is there a way to call the methods with an explicit full method name from JNI (rather than relying on the package based prefix?) BTW, I did an objdump of the so file, and indeed there is a symbol like this :
|
Oh, it already works if you just place |
That's exactly the way JNI declarations work, if you place it into |
Haha, you are probably right. Thanks for your help @beraldofilippo ! |
Heya,
I am making an Android app, with similar functionality as the demo app in terms of dlib calls. I started from a new project, using the Gradle dependency. Everything works fine including JNI calls to DetFace etc. but I also want to use the JNI functions of the ImageUtils class and am not sure how I can include these? Every time I run them, I get an Implementation not found error. It seems the binaries are not inside the libpeople_det.so, right? Where are they then? I would expect to see a .so file somewhere, and a System.loadLibrary in ImageUtils, but I do not find either of them. Could anyone help me out? Thanks a lot.
The text was updated successfully, but these errors were encountered: