genode/repos/libports
Martin Stein c47a6b0830 depot_autopilot: simplify success-criterion syntax
* Removes the <event> tag from all test package runtime files and replaces the
  contained <timeout> and <log> sub-tags with the new tags <succeed> and
  <fail>. If a <succeed> or <fail> tag has a content, it defines a log pattern
  that should be recognized and render the test failed or successful. If a
  <succeed> or <fail> tag has an attribute after_seconds that is not set to 0,
  it defines a timeout after which the test should be rendered failed or
  successful.

* Adapts the Depot Autopilot to support the new syntax in the test-package
  runtime files. However, for now, the Depot Autopilot is kept compatible to
  the old syntax as well. If the <events> tag is present, it is prioritized
  over the new syntax.

Fixes #4922
2023-08-21 08:12:01 +02:00
..
doc libports: update doc/libc.txt 2023-05-30 12:03:33 +02:00
include libc: make libc-plugin headers private to libc 2023-05-30 12:03:33 +02:00
lib stdcxx: add missing symbol 2023-06-16 11:24:26 +02:00
ports mesa: remove 'printf' from 'iris_bufmgr_tmp.patch' 2023-06-16 11:24:26 +02:00
recipes depot_autopilot: simplify success-criterion syntax 2023-08-21 08:12:01 +02:00
run net tests: raise nic_drv/drivers cap quota 2023-08-21 08:12:01 +02:00
src mesa: remove 'printf' from 'iris_bufmgr_tmp.patch' 2023-06-16 11:24:26 +02:00
README Update README files 2023-03-13 14:32:53 +01:00

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


Usage
-----

The tool './tool/ports/prepare_port' in the toplevel directory automates the
task of downloading and preparing the 3rd-party source codes. One can select
individual ports 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 via the 'libc' port. The libc, in turn, depends on
the 'os' repository for its back end.