Hi, all,
We pushed the kernel project for the following devices:
Tag | Project| Branch
| device
android-lego-7.1.1_r0.12 | kernel/msm |
android-msm-shamrock-3.10-nougat-mr1-release | shamrock NNK30
--
--
You received this
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
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
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
[ 2% 2026/87160] Import includes file:
out/host/linux-x86/obj/EXECUTABLES/sepolicy-analyze_intermediates/import_includes
[ 2% 2027/87160] target Prebuilt:
system_core_charger_res_images_battery_fail.png