mirror of
https://github.com/genodelabs/genode.git
synced 2025-01-12 07:52:44 +00:00
c450ddcb3d
This patch removes possible ambiguities with respect to the naming of kernel-dependent binaries and libraries. It also removes the use of kernel-specific global side effects from the build system. The reach of kernel-specific peculiarities has thereby become limited to the actual users of the respective 'syscall-<kernel>' libraries. Kernel-specific build artifacts are no longer generated at magic places within the build directory (like okl4's includes, or the L4 build directories of L4/Fiasco and Fiasco.OC, or the build directories of various kernels). Instead, such artifacts have been largely moved to the libcache. E.g., the former '<build-dir>/l4/' build directory for the L4 build system resides at '<build-dir>/var/libcache/syscall-foc/build/'. This way, the location is unique to the kernel. Note that various tools are still generated somewhat arbitrarily under '<build-dir>/tool/' as there is no proper formalism for building host tools yet. As the result of this work, it has become possible to use a joint Genode build directory that is usable with all kernels of a given hardware platform. E.g., on x86_32, one can now seamlessly switch between linux, nova, sel4, okl4, fiasco, foc, and pistachio without rebuilding any components except for core, the kernel, the dynamic linker, and the timer driver. At the current stage, such a build directory must still be created manually. A change of the 'create_builddir' tool will follow to make this feature easily available. This patch also simplifies various 'run/boot_dir' plugins by removing the option for an externally hosted kernel. This option remained unused for many years now. Issue #2190 |
||
|---|---|---|
| .. | ||
| spec | ||
| base-common.inc | ||
| base.inc | ||
| base.mk | ||
| component_entry_point.mk | ||
| cxx.mk | ||
| ld-platform.inc | ||
| ld.mk | ||
| ldso-startup.mk | ||
| platform.mk | ||
| README | ||
| startup.inc | ||
| syscall.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'.