genode/repos/os/src/init/target.mk

TARGET   = init
SRC_CC   = main.cc child.cc server.cc
LIBS     = base
INC_DIR += $(PRG_DIR)

CONFIG_XSD = config.xsd
init: refactoring into multiple files This patch splits the implementation of init into several headers to make the implementation easier to digest and to maintain. 2017-03-03 16:57:41 +01:00			`TARGET = init`
init: service forwarding This patch equips init with the ability to act as a server that forwards session requests to its children. Session requests can be routed depending of the requested service type and the session label originating from init's parent. The feature is configured by one or multiple <service> nodes hosted in init's <config> node. The routing policy is selected by via the regular server-side policy-selection mechanism, for example: <config> ... <service name="LOG"> <policy label="noux"> <child name="terminal_log" label="important"/> </policy> <default-policy> <child name="nitlog"/> </default-policy> </service> ... </config> Each policy node must have a <child> sub node, which denotes name of the server with the 'name' attribute. The optional 'label' attribute defines the session label presented to the server, analogous to how the rewriting of session labels works in session routes. If not specified, the client-provided label is presented to the server as is. Fixes #2247 2017-03-08 10:21:49 +01:00			`SRC_CC = main.cc child.cc server.cc`
init: refactoring into multiple files This patch splits the implementation of init into several headers to make the implementation easier to digest and to maintain. 2017-03-03 16:57:41 +01:00			`LIBS = base`
			`INC_DIR += $(PRG_DIR)`
run: target-specific config schemata The run tool now by default checks configurations with target-specific XML schemata. Each component may define a config schema file in its target.mk via the CONFIG_XSD variable. When the run tool has checked an configuration of an init instance, it additionally goes through the start nodes of the config. For each start node it checks whether there is an XSD file that matches. If so, the run tool also checks the config of the start node (if existant). This is done recursively. I.e., also the child configs of a sub-init of a sub-init of the top-level init receive a config check. Issue #2600 2017-12-03 18:48:40 +01:00
			`CONFIG_XSD = config.xsd`