genode

History

Norman Feske 65f75589e9 libc: configurable initial FDs The libc already supports the configuration of 'stdin', 'stdout', and 'stderr' using '<libc>' config attributes. This patch equips the libc with the additional ability to pre-initialize any other file descriptor. A file descriptor is configured as follows: <config> ... <libc ...> <fd id="3" path="/dev/log" writeable="yes" readable="no" seek="10"/> ... </libc> </config> Furthermore, this patch moves the FD initialization code from the VFS plugin to the libc kernel initialization because opening the FDs depends on 'malloc' ('strdup'), which should not be used at early 'Libc::Kernel' initialization time. Issue #3478		2019-08-28 14:18:44 +02:00
..
doc	tool: remove deprecated 'make prepare' mechanism	2016-03-17 17:02:04 +01:00
include	libc: configurable initial FDs	2019-08-28 14:18:44 +02:00
lib	ada-runtime: update to 1.1	2019-08-21 13:25:25 +02:00
ports	ada-runtime: update to 1.1	2019-08-21 13:25:25 +02:00
recipes	depot: update recipe hashes	2019-08-21 13:25:26 +02:00
run	system_rtc.run: use packages	2019-08-21 13:25:25 +02:00
src	libc: configurable initial FDs	2019-08-28 14:18:44 +02:00
README	README update	2016-08-30 17:24:00 +02:00

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.