mirror of
https://github.com/genodelabs/genode.git
synced 2024-12-22 15:02:25 +00:00
fae63f4fa9
This patch simplifies the way of how Genode's base libraries are organized. Originally, the base API was implemented in the form of many small libraries such as 'thread', 'env', 'server', etc. Most of them used to consist of only a small number of files. Because those libraries are incorporated in any build, the checking of their inter-dependencies made the build process more verbose than desired. Also, the number of libraries and their roles (core only, non-core only, shared by both core and non-core) were not easy to capture. Hereby, the base libraries have been reduced to the following few libraries: - startup.mk contains the startup code for normal Genode processes. On some platform, core is able to use the library as well. - base-common.mk contains the parts of the base library that are identical by core and non-core processes. - base.mk contains the complete base API implementation for non-core processes Consequently, the 'LIBS' declaration in 'target.mk' files becomes simpler as well. In the most simple case, only the 'base' library must be mentioned. Fixes #18 |
||
|---|---|---|
| .. | ||
| arm | ||
| x86_32 | ||
| x86_64 | ||
| cxx.mk | ||
| platform.mk | ||
| README | ||
| startup.inc | ||
| syscall.mk | ||
| toolchain_stdcxx.mk | ||
This directory contains library description files. Each '<libname>.mk' file holds the instruction for building the library '<libname>'. These makefiles are never used directly but they are called from the build system when required. When called, the build system passes the following variables: :'BASE_DIR': This is the base directory of the source tree. Source codes are specified by setting the 'SRC_CC' and 'SRC_C' variables. The source code locations must be specified via 'vpath'. A library can include other libraries by setting the 'LIBS' variable. Each '<libname>.mk' file must include the 'lib.mk' role file: ! include $(BASE_DIR)/mk/lib.mk Libraries implementing one and the same library interface may have specific implementations for different platforms. Such platform-specific '<libname>.mk' files should be placed into corresponding subdirectories. For example, the 'linux'-specific implementation of the 'server' library resides in the 'linux/' subdirectory. The build system automatically searches the right '<libname>.mk' file by evaluating the 'SPECS' configuration variable. If 'SPECS' is set to 'host linux', the build system will look into the directories './', './host', and './linux'.