It would require more debugging to find the exact cause. I can't think of anything specific at the top of my head.
For starters, instead of dynamically loading the library, can you link the library to your test app executable to see if that works? -Ravi On Dec 29, 7:55 am, waterblood <[email protected]> wrote: > Thanks for your reply. > > I have set the LOCAL_PRELINK_MODULE := false and include $ > (BUILD_SHARED_LIBRARY) in my android.mk to build my.so > But when I use a dlopen() in a test c app to open that my.so. Got a > fail message "cannot find the library". I have checked the my.so have > been put into /system/lib. Do you have any idea about this? > > Best Regards > > On Dec 29, 10:30 am, rktb <[email protected]> wrote: > > > If you want to prelink the shared library, yes. This is the default > > option. > > > If not, to bypass the prelinking step, one would need to add the > > following line in their Android.mk that is creating the shared > > library: > > > LOCAL_PRELINK_MODULE := false > > <<< > > > -Ravi > > > On Dec 29, 7:11 am, waterblood <[email protected]> wrote: > > > > Hello all, > > > > There are so files entry defined in /build/core/prelink-linux- > > > arm.map. my question is when I add a new dynamic library, should i > > > also add an entry for this so in prelink-linux-arm.map? > > > > Thanks for any replay! > > > Guoyin Chen --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "android-framework" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-framework?hl=en -~----------~----~----~----~------~----~------~--~---
