我正在一个
Android应用程序中工作,其中一个共享库(我在Android Studio中构建,我们称之为libA.so)由供应商动态加载另一个共享库提供程序(让我们称之为libB.so).我知道我不应该在我的应用程序中使用多个C运行时库(
https://developer.android.com/ndk/guides/cpp-support.html#important_considerations),因此我们决定在两个库中使用c _shared.
构建AOSP时,libB.so(由供应商提供的)编译和链接(供应商坚持以这种方式构建库,对此无能为力). libB.so的makefile正在将STL标志设置为c _shared:
LOCAL_NDK_STL_VARIANT := c++_shared
当我查看libB.so库中的NEEDED标记时,我可以看到对libc .so的依赖
0x0000000000000001 (NEEDED) Shared library: [libdl.so]
0x0000000000000001 (NEEDED) Shared library: [libc++.so]
0x0000000000000001 (NEEDED) Shared library: [libc.so]
0x0000000000000001 (NEEDED) Shared library: [libm.so]
0x000000000000000e (SONAME) Library soname: [libB.so]
当我运行readelf -d libc .so来检查AOSP的libc的内容时,我得到了这个
Dynamic section at offset 0xe4b40 contains 29 entries:
Tag Type Name/Value
0x0000000000000003 (PLTGOT) 0xe6310
0x0000000000000002 (PLTRELSZ) 22128 (bytes)
0x0000000000000017 (JMPREL) 0x39ff8
0x0000000000000014 (PLTREL) RELA
0x0000000000000007 (RELA) 0x2ce58
0x0000000000000008 (RELASZ) 53664 (bytes)
0x0000000000000009 (RELAENT) 24 (bytes)
0x000000006ffffff9 (RELACOUNT) 380
0x0000000000000006 (SYMTAB) 0x238
0x000000000000000b (SYMENT) 24 (bytes)
0x0000000000000005 (STRTAB) 0xdeb8
0x000000000000000a (STRSZ) 102917 (bytes)
0x000000006ffffef5 (GNU_HASH) 0x270c0
0x0000000000000001 (NEEDED) Shared library: [libdl.so]
0x0000000000000001 (NEEDED) Shared library: [libc.so]
0x0000000000000001 (NEEDED) Shared library: [libm.so]
0x000000000000000e (SONAME) Library soname: [libc++.so]
0x000000000000001a (FINI_ARRAY) 0xe08e0
0x000000000000001c (FINI_ARRAYSZ) 8 (bytes)
0x0000000000000019 (INIT_ARRAY) 0xe5b38
0x000000000000001b (INIT_ARRAYSZ) 8 (bytes)
0x000000000000001e (FLAGS) BIND_NOW
0x000000006ffffffb (FLAGS_1) Flags: NOW
0x000000006ffffff0 (VERSYM) 0x2bb7c
0x000000006ffffffc (VERDEF) 0x2cddc
0x000000006ffffffd (VERDEFNUM) 1
0x000000006ffffffe (VERNEED) 0x2cdf8
0x000000006fffffff (VERNEEDNUM) 2
0x0000000000000000 (NULL) 0x0
我知道NDK也提供了libc .so,但是当我在Android NDK中分发的库中运行相同的命令时,我收到一个错误
readelf: Error: libc++.so: Failed to read file header
如果我没弄错的话,那是因为在NDK中,libc .so实际上是一个链接器脚本.
libA.so(我用我的应用程序构建并加载libB.so)最终依赖于libc _shared.so
Dynamic section at offset 0x4bca50 contains 28 entries:
Tag Type Name/Value
0x0000000000000001 (NEEDED) Shared library: [libdl.so]
0x0000000000000001 (NEEDED) Shared library: [liblog.so]
0x0000000000000001 (NEEDED) Shared library: [libc++_shared.so]
0x0000000000000001 (NEEDED) Shared library: [libc.so]
0x000000000000000e (SONAME) Library soname: [libA.so]
我不认为我可以(或应该)在我的应用程序中捆绑libc .so和libc _shared.so.
那么,AOSP的libc.是否与NDK的libc _shared.so相同?
有人知道为什么即使使用了LOCAL_NDK_STL_VARIANT:= c _shared,AOSP也会为libc .so而不是libc _shared.so添加动态依赖?我应该要求我的提供商链接libc _shared.so吗?也许有人有更好的建议来解决这种依赖性不匹配问题.