| commit | 6dc2c1dda60a7381fa886ac8f7f10bf9ada3eda2 | [log] [tgz] |
|---|---|---|
| author | Jooyung Han <jooyung@google.com> | Wed Jan 26 12:41:21 2022 +0000 |
| committer | Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com> | Wed Jan 26 12:41:21 2022 +0000 |
| tree | 98c5892bda611c433da2537161f76754fe3086c4 | |
| parent | bf2fc0676d96ef84edc0f220d171cda0887db24c [diff] | |
| parent | a8df5054bd16731f64a28010338075e84e41ef79 [diff] |
Make linkerconfig_diff_test faster am: a8df5054bd Original change: https://android-review.googlesource.com/c/platform/system/linkerconfig/+/1961206 Change-Id: Ib40751a1041e30770ace018da9420b836d23b052
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" ]
}
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.