f54c85e045
This patch decouples the kernel-specific implementation of the dynamic linker from its kernel-agnostic binary interface. The name of the kernel-specific dynamic linker binary now corresponds to the kernel, e.g., 'ld-linux.lib.so' or 'ld-nova.lib.so'. Applications are no longer linked directly against a concrete instance of the dynamic linker but against a shallow stub called 'ld.lib.so'. This stub contains nothing but the symbols provided by the dynamic linker. It thereby represents the Genode ABI. At system-integration time, the kernel-specific run/boot_dir back ends integrate the matching the kernel-specific variant of the dynamic linker as 'ld.lib.so' into the boot image. The ABI symbol file for the dynamic linker is located at 'base/lib/symbols/ld'. It contains the joint ABI of all supported architectures. The new utility 'tool/abi_symbols' eases the creation of such an ABI symbol file for a given shared library. Its result should be manually inspected and edited as needed. The patch removes the 'syscall' library from 'base_libs.mk' to avoid polluting the kernel-agnostic ABI with kernel-specific interfaces. Issue #2190 Issue #2195 |
||
|---|---|---|
| .. | ||
| spec | ||
| README | ||
| base-common.inc | ||
| base.inc | ||
| base.mk | ||
| component_entry_point.mk | ||
| cxx.mk | ||
| ld-platform.inc | ||
| ld.mk | ||
| ldso-startup.mk | ||
| platform.mk | ||
| startup.inc | ||
| syscall.mk | ||
README
This directory contains library description files. Each '<libname>.mk' file holds the instruction for building the library '<libname>'. These makefiles are never used directly but they are called from the build system when required. When called, the build system passes the following variables: :'BASE_DIR': This is the base directory of the source tree. Source codes are specified by setting the 'SRC_CC' and 'SRC_C' variables. The source code locations must be specified via 'vpath'. A library can include other libraries by setting the 'LIBS' variable. Each '<libname>.mk' file must include the 'lib.mk' role file: ! include $(BASE_DIR)/mk/lib.mk Libraries implementing one and the same library interface may have specific implementations for different platforms. Such platform-specific '<libname>.mk' files should be placed into corresponding subdirectories. For example, the 'linux'-specific implementation of the 'server' library resides in the 'linux/' subdirectory. The build system automatically searches the right '<libname>.mk' file by evaluating the 'SPECS' configuration variable. If 'SPECS' is set to 'host linux', the build system will look into the directories './', './host', and './linux'.