genode-ehmry

History

Emery Hemingway 3757fa0c7d New VFS plugin for emulating POSIX pipes Add a new plugin for creating pipes between pairs of VFS handles. It is intended to replace the libc_pipe plugin, one of the last remaining libc plugins. In contrast to the libc_pipe plugin, this plugin defers cross-handle notification until I/O signal handling rather than block and unblock readers using a semaphore. This is a performance regression in the case of multiple threads blocking on a pipe, but shall be an intermediate mechanism pending renovations within the libc VFS and threading layers. As a side effect, threads blocked on a pipe might not be resumed until the main thread suspends and dispatches I/O signals. The "test-libc_pipe" test has been adjusted to use the VFS pipe plugin and tests both local pipes and pipes hosted remotely in the VFS server. Fix #2303		2019-06-04 19:09:45 +02:00
..
doc	tool: remove deprecated 'make prepare' mechanism	2016-03-17 17:02:04 +01:00
include	VFS lwIP: restart DHCP with link-state changes	2019-05-29 14:19:04 +02:00
lib	Remove libc_terminal	2019-05-29 14:19:04 +02:00
ports	libc: mktime signed overflow	2019-05-29 10:20:52 +02:00
recipes	New VFS plugin for emulating POSIX pipes	2019-06-04 19:09:45 +02:00
run	Add note on PCAP dump to run/fetchurl.inc	2019-05-29 14:19:04 +02:00
src	New VFS plugin for emulating POSIX pipes	2019-06-04 19:09:45 +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.