Keep vendor.apk in /system/app (notee that it wont work at /system/ level), so it will be automatically installed by package manager on first boot, and extract the associated libraries to /data/data/<vendor-apk>/lib folder .
This shou;d've worked good. but, if you expect vendor.so to go with rest of the system, it should be available under global lib path (/system/lib folder) in that case, you can add vendor.so to your build system, and add it to your project tree., say, sample Android.mk command will look like, PRODUCT_COPY_FILES += vendor.so:/system/lib/vendor.so you can refer such .mk exports from TI make files : http://git.omapzoom.org/?p=device/ti/blaze.git;a=blob;f=AndroidBoard.mk;h=87eccadddbdb9fdf4876c3bfb9d941e9ae0a5bc3;hb=froyo -- Regards, Deva www.bittoggler.com On Fri, Oct 29, 2010 at 3:01 AM, fadden <fad...@android.com> wrote: > On Oct 28, 4:19 am, Eric <sen...@gmail.com> wrote: >> But if I use adb install vendor.apk afterward, the package manager >> will unpack vendor.so correctly, that means the vendor.apk is working >> fine. So is it not appropriate to pack Android App with JNI libs >> inside system applications? > > No. The assumption is that, if you're installing the app in /system, > you will also be installing the .so in /system/lib. > > -- > unsubscribe: android-porting+unsubscr...@googlegroups.com > website: http://groups.google.com/group/android-porting > -- unsubscribe: android-porting+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-porting
