genode

mirror of https://github.com/genodelabs/genode.git synced 2024-12-20 14:13:09 +00:00

History

Norman Feske 62bb85255a libc_lwip: use libc's 'get-/freeaddrinfo()' This patch reduces problems when connecting Arora to lighttpd via nic_bridge. Patch by Christian Prochaska		2013-02-11 12:01:27 +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	libc_lwip: use libc's 'get-/freeaddrinfo()'	2013-02-11 12:01:27 +01:00
ports	Update url of freetype-2.3.9	2013-01-12 15:20:13 +01:00
run	nic_bridge: Add tests for static IP address configuration	2013-01-24 11:35:56 +01:00
src	libc_lwip: use libc's 'get-/freeaddrinfo()'	2013-02-11 12:01:27 +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.