genode

History

Martin Stein 8ab0a5c795 nic_router.run: avoid use of 'string cat' It seems that our buildbot has a problem with the TCL command 'string cat'. In most cases it is not necessary anyway as we can use the "" enclosure instead. It unfolds inline procedure calls and variables automatically. We don't want to use "" only in cases where the literal shall contain many " characters itself as it is the case for XML configs. Then we use the 'append' command and a helper variable instead. Ref #2193		2017-02-28 12:59:28 +01:00
..
doc	tool: remove deprecated 'make prepare' mechanism	2016-03-17 17:02:04 +01:00
include	libc: remove global config accessor	2017-02-28 12:59:27 +01:00
lib	libc: select support for components	2017-02-28 12:59:17 +01:00
ports	jitterentropy: remove deprecated env() usage	2017-02-23 14:54:43 +01:00
run	nic_router.run: avoid use of 'string cat'	2017-02-28 12:59:28 +01:00
src	libc: remove global config accessor	2017-02-28 12:59:27 +01: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.