mirror of
https://github.com/genodelabs/genode.git
synced 2024-12-19 13:47:56 +00:00
852ab79359
This patch untangles the interplay of the base library and the libc during the exit handling. - The CXA ABI for the atexit handling is now provided by the libc. For plain Genode components without libc dependency, __cxa_atexit is a no-op, which is consistent with Genode's notion of components. - The 'abort' implementation of the base library no longer calls 'genode_exit' but merely 'sleep_forever'. This way, the cxx library no longer depends on a 'genode_exit' implementation. - The libc provides 'atexit' support by storing metadata on the libc kernel's heap now, thereby eliminating the former bounded maximum number of atexit handlers. - Shared-library dtors are no longer called via the atexit mechanism by explicitly by the dynamic linker. This slightly changes the call order of destructors (adjustment of the ldso test). Functions marked as destructors are called after the atexit handlers now. - The libc executes atexit handlers in the application context, which supports the I/O operations in those handles, in particular the closing of file descriptors. Fixes #3851 |
||
|---|---|---|
| .. | ||
| doc | ||
| include | ||
| lib | ||
| ports | ||
| recipes | ||
| run | ||
| src | ||
| README | ||
This directory contains ports of popular 3rd-party software to Genode. Usage ----- The tool './tool/ports/prepare_port' in the toplevel directory automates the task of downloading and preparing the library source codes. You can select individual packages that have to be prepared by specifying their base names (without the version number) as command-line argument. For example, the following command prepares both the C library and the Freetype library: ! ./tool/ports/prepare_port libc freetype To compile and link against 3rd-party libraries of the 'libports' repository, you have to include the repository into the build process by appending it to the 'REPOSITORIES' declaration of your '<build-dir>/etc/build.conf' file. Under the hood -------------- For each library, there is a file contained in the 'libports/ports/' subdirectory. The file is named after the library and contains the library-specific rules for downloading the source code and installing header files. How does 'libports' relate to the other repositories? ----------------------------------------------------- Most libraries hosted in the 'libports' repository expect a complete C library, which is provided with the 'libc' package. Please do not forget to prepare the libc package when using any of the other libports packages. The libc, in turn, depends on the 'os' repository for its back end. Because the 'os' repository is the home of the dynamic linker, libraries contained in 'libports' are safe to assume the presence of the dynamic linker and, thus, should be built as shared libraries.