genode

History

Emery Hemingway a635873568 VFS: Replace global response handlers with local handlers Replace the I/O response handler that is passed to the VFS at construction with an object that is dynamically attached to handles. This object shall also accept read-ready notifications, and plugins are encouraged to keep handles awaiting ready-ready notifications separate from handles that await I/O progress. Replace the use of handle lists in plugins with handle queues, this makes the code easier to understand and the ordering of notifications to the application more explicit. These changes replace the use of the Post_signal_hook from all VFS plugins, applications must assume that read-ready and I/O notifications occur during I/O signal dispatch and use an Io_progress_handler at its entrypoints to defer response until after signal dispatching. Fix #3257		2019-04-09 12:30:34 +02:00
..
doc	tool: remove deprecated 'make prepare' mechanism	2016-03-17 17:02:04 +01:00
include	qt5: remove deprecated APIs	2019-02-26 14:38:03 +01:00
lib	rustc: select ARM target correctly (fix #3087 )	2019-04-01 19:33:48 +02:00
ports	Use https URLs for qt5 downloads	2019-03-18 15:56:23 +01:00
recipes	Print error locations in test-libc_connect	2019-04-09 12:30:34 +02:00
run	smartcard.run: increase caps for usb_drv	2019-04-01 19:33:52 +02:00
src	VFS: Replace global response handlers with local handlers	2019-04-09 12:30:34 +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.