commit | ea871a57d120d68f8bd3cc17463ec231c819e478 | [log] [tgz] |
---|---|---|
author | Kiyoung Kim <kiyoungkim@google.com> | Wed May 08 01:01:51 2024 +0000 |
committer | Kiyoung Kim <kiyoungkim@google.com> | Fri May 24 11:52:46 2024 +0900 |
tree | d1c3a700ef9b16a9cbb295dd877e2c79038127d3 | |
parent | b1dcd6028ae098f887c3d0132c94504f25b9857f [diff] |
Update linkerconfig diff tests As VNDK is deprecated by default, update diff test cases to run without VNDK except some cases (Vendor-only VNDK available). Bug: 330100430 Change-Id: Ib17789ee7fef4c778e9fa9919940ef490d33e896 Merged-In: Ib17789ee7fef4c778e9fa9919940ef490d33e896 Test: updated with rundiff.sh
Linkerconfig is a program to generate linker configuration based on the runtime environment. Linkerconfig generates one or more ld.config.txt files and some other files under /linkerconfig during init. Linker will read this generated configuration file(s) to find out link relationship between libraries and executable.
TODO: explain inputs (e.g. /system/etc/public.libraries.txt, /apex/apex-info-list.xml, ..)
Linker configuration file can be used to add extra information while linkerconfig creates linker configuration with the module. This module can be defined as linker_config
from Soong, and it will be translated as protobuf file at build time.
A linker configuration file(linker.config.json) is compiled into a protobuf at build time by conv_linker_config
. You can find the compiled file under <base>/etc/linker.config.pb
. For example, /apex/com.android.art/etc/linker.config.pb
is a configuration for the com.android.art
APEX.
/system/etc/linker.config.pb
(or its source module system_linker_config
) is special because its provideLibs
key is generated at build time.
linker.config.json file is in json format which can contain properties as below.
Property Name | Type | Description | Allowed module |
---|---|---|---|
permittedPaths | List | Additional permitted paths | APEX |
visible | bool | Force APEX namespace to be visible from all sections if the value is true | APEX |
provideLibs | List | Libraries providing from the module | System |
requireLibs | List | Libraries required from the module | System |
{ "permittedPaths" : [ "/a", "/b/c", "/d/e/f"], "visible": true }
{ "provideLibs" : [ "a.so", "b.so", "c.so" ], "requireLibs" : [ "foo.so", "bar.so", "baz.so" ] }
linkerconfig
reads both /system/etc/public.libraries.txt
and /vendor/etc/public.libraries.txt
to identify libraries that are provided by APEX and accessible from apps via libnativeloader
.
linkerconfig
generates apex.libraries.config.txt
file which lists public libraries provided APEX. libnativeloader
, then, links those libraries from classloader-namespace to providing APEXes.
TODO: a few words about the files
Check ld.config.format.md.
The file describes libraries exposed from APEXes. libnativeloader is the main consumer of this file.
# comment line jni com_android_foo libfoo_jni.so public com_android_bar libbar.so:libbaz.so
The file is line-based and each line consists of tag apex_namespace library_list
.
tag
explains what library_list
is.apex_namespace
is the namespace of the apex. Note that it is mangled like com_android_foo
for the APEX(“com.android.foo”).library_list
is colon-separated list of library names.tag
is jni
, library_list
is the list of JNI libraries exposed by apex_namespace
.tag
is public
, library_list
is the list of public libraries exposed by apex_namespace
. Here, public libraries are the libs listed in /system/etc/public.libraries.txt.