genode

History

Norman Feske fae63f4fa9 Merge base libraries into a single library This patch simplifies the way of how Genode's base libraries are organized. Originally, the base API was implemented in the form of many small libraries such as 'thread', 'env', 'server', etc. Most of them used to consist of only a small number of files. Because those libraries are incorporated in any build, the checking of their inter-dependencies made the build process more verbose than desired. Also, the number of libraries and their roles (core only, non-core only, shared by both core and non-core) were not easy to capture. Hereby, the base libraries have been reduced to the following few libraries: - startup.mk contains the startup code for normal Genode processes. On some platform, core is able to use the library as well. - base-common.mk contains the parts of the base library that are identical by core and non-core processes. - base.mk contains the complete base API implementation for non-core processes Consequently, the 'LIBS' declaration in 'target.mk' files becomes simpler as well. In the most simple case, only the 'base' library must be mentioned. Fixes #18		2013-02-19 14:45:55 +01:00
..
doc	Imported Genode release 11.11	2011-12-22 16:19:25 +01:00
include	Update copyright headers to 2013	2013-01-10 21:44:47 +01:00
lib	Merge base libraries into a single library	2013-02-19 14:45:55 +01:00
ports	Update url of freetype-2.3.9	2013-01-12 15:20:13 +01:00
run	moon.run: Increase quota of 'test-moon'	2013-02-14 17:23:47 +01:00
src	Merge base libraries into a single library	2013-02-19 14:45:55 +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.