genode/libports
Norman Feske 13d4108fea Unify 'Signal_dispatcher' interfaces
Several users of the signal API used custom convenience classes to
invoke signal-handling functions on the reception of incoming signals.
The 'Signal_dispatcher' pattern turned out to be particularly useful. To
avoid the duplication of this code across the code base, this patch
adds the interface to 'base/signal.h'.

Furthermore, the patch changes the 'Signal::num()' return type from int
to unsigned because negative numbers are meaningless here.

Fixes #511
2013-01-10 21:09:14 +01:00
..
doc Imported Genode release 11.11 2011-12-22 16:19:25 +01:00
include libports: stdcxx 4.7.2 update 2012-11-14 16:55:33 +01:00
lib libports: stdcxx 4.7.2 update 2012-11-14 16:55:33 +01:00
ports libports: stdcxx 4.7.2 update 2012-11-14 16:55:33 +01:00
run moon: provide IO_MEM for base-hw timers 2012-11-29 09:55:09 +01:00
src Unify 'Signal_dispatcher' interfaces 2013-01-10 21:09:14 +01:00
tool/mesa Imported Genode release 11.11 2011-12-22 16:19:25 +01:00
Makefile prepare: Serialize preparation in Makefile 2012-12-05 14:02:18 +01:00
README Imported Genode release 11.11 2011-12-22 16:19:25 +01:00

README

This directory contains ports of popular 3rd-party software to Genode.


Usage
-----

At the root of the 'libports' repository, there is 'Makefile' automating the
task of downloading and preparing the library source codes. By just typing
'make', you get an overview of the available libraries and further
instructions.

In the common case, you might just want to prepare all packages by issuing:
! make prepare

Alternatively, you can select individual packages to prepare 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:
! make prepare PKG="libc freetype"

After having prepared the 'libports' repository, you are ready 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.