Note that there are some explanatory texts on larger screens.

plurals
  1. POandroid native lib not installed with APK
    primarykey
    data
    text
    <p>I've made an android library project that uses some native libraries.</p> <p>I've made the jni wrapper and put the native libs (.so) in the libs// folders. The native libs are compiled using cmake, for armeabi, armeabi-v7a, x86 and mips.</p> <p>I export this project to a jar and put this jar into a "normal" android project. I then export this project to an apk and can see that my libs are bundles into it.</p> <p>However, when i install the apk, the libs corresponding to the device are not copied into /data/data/com.my.app/lib and obviously, running the app complains about not finding the libs (UnsatisfiedLinkError).</p> <p>I've search through SO and everywhere i can but found no answer that solved my case.</p> <p>i'm using Eclipse, btw</p> <p>Thanks for your help</p> <p><strong>UPDATE</strong></p> <p>OK, i've read the doc in the ndk and seen the examples, and unfortunately, i can't see the solution.</p> <p>The ndk build the c code into shared libs and places them into the appropriated location in the project. But it doesn't generate anything that says that the libs must be installed with the apk.</p> <p>My goal is to provide an android library (so a jar), that can be included within an android application. I don't see the real difference between what i'm doing (compile the c libs using cmake and package the jni and java compiled classes into a jar) and what is done with android.mk</p> <p>If you see what i'm missing, feel free to tell me (even if its obvious).</p> <p>thanks</p> <p><strong>UPDATE</strong></p> <p>i've made a dirty hack: in the libs folder of my application, i've put the jar file containing my classes and my native libs and a copy of the .so files for each arch. Suprise, the libs are no installed in /data/data/com.me.myapp/lib</p> <p>It seems to confirm that it's a packaging problem.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload