genode/libports
Christian Prochaska c39e5557c5 libports: stdcxx 4.7.2 update
Fixes #469.
2012-11-14 16:55:33 +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 Python: use 'libc-rom' plugin 2012-10-08 15:10:22 +02:00
src libports: add dup() to libc 2012-11-14 16:52:33 +01:00
tool/mesa Imported Genode release 11.11 2011-12-22 16:19:25 +01:00
Makefile Check for required tools on 'make prepare' 2012-05-29 13:55:00 +02:00
README Imported Genode release 11.11 2011-12-22 16:19:25 +01:00

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.