genode

History

Christian Helmuth db3a5a3b02 Some rounds of write/read in libc fs test The test performs several rounds of write-read cycles with the following configuration attributes in a <write-read> config node rounds determines the number of rounds (default is 4) size determines the number of bytes written/read in one round (default is 4 MiB) buffer_size determines the size of the write-read buffer (default is 32 KiB) In one round the test writes and reads "size/buffer_size" times from/into a buffer_size'd buffer.		2015-11-18 12:22:05 +01:00
..
doc	Move repositories to 'repos/' subdirectory	2014-05-14 16:08:00 +02:00
include	lwip: log thread and sleep forever in assert()	2015-09-30 12:20:40 +02:00
lib	qt5: add clipboard support	2015-11-09 13:17:56 +01:00
ports	lwip: patch for resetting write offset	2015-10-06 12:18:57 +02:00
run	Some rounds of write/read in libc fs test	2015-11-18 12:22:05 +01:00
src	Some rounds of write/read in libc fs test	2015-11-18 12:22:05 +01:00
Makefile	Unify 'make prepare' between libports and ports	2014-05-14 16:08:00 +02:00
README	Move repositories to 'repos/' subdirectory	2014-05-14 16:08:00 +02: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.