genode

History

Norman Feske 4b46abf813 base: rm first-class support for static binaries This patch removes the detection of statically linked executables from the base framework. It thereby fixes the corner cases encountered with Sculpt when obtaining the binaries of the runtime from the depot_rom service that is hosted within the runtime. Statically linked binaries and hybrid Linux/Genode (lx_hybrid) binaries can still be started by relabeling the ROM-session route of "ld.lib.so" to the binary name, pretending that the binary is the dynamic linker. This can be achieved via init's label rewriting mechanism: <route> <service name="ROM" unscoped_label="ld.lib.so"> <parent label="test-platform"/> </service> </route> However, as this is quite cryptic and would need to be applied for all lx_hybrid components, the patch adds a shortcut to init's configuration. One can simply add the 'ld="no"' attribute to the <start> node of the corresponding component: <start name="test-platform" ld="no"/> Fixes #2866		2018-08-02 14:36:38 +02:00
..
doc	tool: remove deprecated 'make prepare' mechanism	2016-03-17 17:02:04 +01:00
include	libc: remove VFS header dependency in 'component.h'	2018-06-29 10:44:57 +02:00
lib	Remove 'libc' from vfs_jitterentropy dependencies	2018-08-02 14:36:36 +02:00
ports	Convert pdf_view to a Nitpicker client	2018-06-29 10:44:57 +02:00
recipes	depot: update recipe hashes	2018-07-03 09:40:11 +02:00
run	base: rm first-class support for static binaries	2018-08-02 14:36:38 +02:00
src	pthread: 'pthread_join()' improvements	2018-08-02 14:36: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.