genode/repos/base/lib/mk
Norman Feske 61926ebc07 base: introduce platform_init function
The new 'init_platform' function performs the platform-specific
component-local low-level initialization. It allows for the
differentiation between core and regular components as well as
kernel-dependent peculiarities.

This patch introduces a consistent notion of a 'Platform'. Within core,
the 'Platform' contains the kernel-specific initialization. Outside
core, the platform sets up the interplay with the parent component. In
all cases, the platform is constructed while running on the initial
stack.

Issue #4784
2023-03-15 17:05:01 +01:00
..
spec ldso: Fix RISC-V support with 21.05 tool chain 2021-06-25 11:56:22 +02:00
base-common.inc base: remove format strings from API 2023-03-13 14:32:53 +01:00
base.inc base: introduce platform_init function 2023-03-15 17:05:01 +01:00
base.mk Build dynamically linked executables by default 2016-12-14 11:22:27 +01:00
cxx.mk cxx: localize operator new(unsigned long) in supc++.o 2021-02-23 12:02:41 +01:00
ld-platform.inc base: ld-<platform>.abi.so depends on symbol.map 2022-12-01 11:47:32 +01:00
ld.mk base: disregard ld.lib.so stub as build artifact 2022-09-19 14:00:32 +02:00
ldso_so_support.mk Cleanup shared-object support mechanics 2020-05-18 10:16:13 +02:00
README Update README files 2023-03-13 14:32:53 +01:00
startup.inc base: remove platform.mk and syscall.mk 2017-01-13 13:06:53 +01:00
timeout-arm.mk base-hw: problems with timeout lib in src recipe 2022-10-12 11:59:08 +02:00
timeout.mk base-hw: problems with timeout lib in src recipe 2022-10-12 11:59:08 +02:00

This directory contains library-description files.  Each _<libname>.mk_ file
contains the instructions for building the library _<libname>_. The .mk files
are never used directly but they are implicitely processed by the build
system.

Libraries implementing one interface may have specialized implementations for
different CPU architectures. Such architecture-specific _<libname>.mk_ files
are located in corresponding _spec/_ subdirectories. For example, the .mk
files of ARM-specific library variants reside in the _spec/arm/_ subdirectory.
The build system automatically finds the appropriate _<libname>.mk_ file by
evaluating the 'SPECS' build-configuration variable. Whenever the 'SPECS'
variable contains 'arm', the build system considers the _spec/arm/_ directory.