genode

History

Emery Hemingway 72cb71c827 Replace SHA1 hashes of port downloads with SHA256 Now SHA256 has been shown to be an adequate replacement for SHA1, use SHA256 for verifying all port downloads. Ref #2767		2018-05-30 13:36:22 +02:00
..
doc	tool: remove deprecated 'make prepare' mechanism	2016-03-17 17:02:04 +01:00
include	Rename lwip library to lwip_legacy	2018-05-30 13:36:22 +02:00
lib	Rename lwip library to lwip_legacy	2018-05-30 13:36:22 +02:00
ports	Replace SHA1 hashes of port downloads with SHA256	2018-05-30 13:36:22 +02:00
recipes	libc: add suspend and resume_all to symbol map	2018-05-30 13:36:05 +02:00
run	Rename lwip library to lwip_legacy	2018-05-30 13:36:22 +02:00
src	Rename lwip library to lwip_legacy	2018-05-30 13:36:22 +02:00
README	README update	2016-08-30 17:24:00 +02:00

README

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


Usage
-----

The tool './tool/ports/prepare_port' in the toplevel directory automates the
task of downloading and preparing the library source codes. You can select
individual packages that have to be prepared 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:
! ./tool/ports/prepare_port libc freetype

To compile and link against 3rd-party libraries of the 'libports' repository,
you have 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.