genode/libports
Josef Söntgen 9f5c13564c libports: extend FUSE implementation
* add sync method:
  Since file systems tend to have a inbuild caching mechansim we need to
  sync these caches at the end of session when using the fuse_fs server.
  Therefore each FUSE file system port has to implement a Fuse::sync_fs()
  function that executes the necessary actions if requested.

* add symlink check

* allow to check FUSE fs initialization
  This changes the private API of the FUSE implementation. The init_fs
  method now has to return true if the initialization was successful and
  otherwise false. All current users of the API are also changed
  accordingly.

Fixes #1058.
2014-02-28 10:11:09 +01:00
..
doc Imported Genode release 11.11 2011-12-22 16:19:25 +01:00
include libports: extend FUSE implementation 2014-02-28 10:11:09 +01:00
lib test-ldso: test ctors, dtors and atexit functions 2014-02-25 14:58:08 +01:00
ports libport: Fix of download location of pcre 2014-01-08 11:41:07 +01:00
run fs run: fix Qemu ATAPI compatibility test 2013-12-09 14:05:53 +01:00
src libports: extend FUSE implementation 2014-02-28 10:11:09 +01:00
tool Qt5: enable QML support 2013-11-28 08:22:24 +01:00
Makefile ports/libports: Use repository-local PWD 2013-06-12 11:35:13 +02:00
README Imported Genode release 11.11 2011-12-22 16:19:25 +01:00

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


Usage
-----

At the root of the 'libports' repository, there is 'Makefile' automating the
task of downloading and preparing the library source codes. By just typing
'make', you get an overview of the available libraries and further
instructions.

In the common case, you might just want to prepare all packages by issuing:
! make prepare

Alternatively, you can select individual packages to prepare 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:
! make prepare PKG="libc freetype"

After having prepared the 'libports' repository, you are ready 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.