[android-building] Re: Prebuilt library path hardcoded into executable in Android.O using Android.bp

I think i don't have option to install using Cmake. Because The library is provide by third party which was built using Android NDK. And i am trying to integrate in my module in Android source code. Finally i am making the image and flashing to the target. On Tuesday, 27 February 2018 01:22:26

Re: [android-building] Re: Prebuilt library path hardcoded into executable in Android.O using Android.bp

I'm not sure, but I suspect your SONAME is incorrect in your shared library. Make sure that you've specified -Wl,-soname,libmyLibrary.so (or equivalent) when building your library. - Dan On Mon, Feb 26, 2018 at 10:50 AM, Vasishath Kaushal wrote: > I dont know if this

[android-building] Re: Prebuilt library path hardcoded into executable in Android.O using Android.bp

I dont know if this relates to ur case but i have faced a similar problem with cmake in the past. This is a general behaviour of make in which the binaries generated in build tree will always have hardcoded absolute paths to shared libraries. But if one runs make install and then uses those

[android-building] Re: Prebuilt library path hardcoded into executable in Android.O using Android.bp

I tried by setting different ldflags, but couldn't get the solution. Android experts kindlhy give your suggestions. Thanks in Advance Vijay On Monday, 26 February 2018 00:35:28 UTC+5:30, Vijay Ch wrote: > > I have a prebuilt library libmyLibrary.so which is linked against > Myexecutable as