mirror of
https://github.com/mmueller41/genode.git
synced 2026-01-21 20:42:56 +01:00
2533d7b4b6
- remove redundant file system factory - remove dead code block The code was guarded by preprocessor directives checking whether the contrib code define "_USE_MKFS" is 1. As "_USE_MKFS" is not set one for our port of FAT, the code was never executed and can be removed. - remove uneffective config attributes Apparently, the former XML attributes to the plugin 'drive' and 'codepage' had no effect. I tested them in a scenario with the VFS block server on a disk-image boot-module as back end. Regardless of the 'drive' value, the block session label was always "0". Regardless of the 'codepage' value, the FAT on the disk image succeeded to mount when not using '--codepage' for 'mkfs.fat' and failed to mount when using '--codepage' to specify a supported but foreign codepage for 'mkfs.fat' (e.g. "720"). Ref #4220
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.