Modularize Sculpt OS image creation
This patch equips Sculpt with the ability to customize the system image
in very flexible ways.
All customizable aspects of the image have been relocated from the
former sculpt.run script and the accompanied gems/run/sculpt/ directory
to a new location - the sculpt/ directory - which can exist in any
repository. The directory at repos/gems/sculpt/ serves as reference.
The sculpt directory can host any number of <name>-<board>.sculpt files,
each containing a list of ingredients to be incorporated into the
Sculpt system image. The <name> can be specified to the sculpt.run
script. E.g., the following command refers to the 'default-pc.sculpt'
file:
make run/sculpt KERNEL=nova BOARD=pc SCULPT=default
If no 'SCULPT' argument is supplied, the value 'default' is used.
A .sculpt file refers to a selection of files found at various
subdirectries named after their respective purpose. In particular, There
exists a subdirectory for each file in Sculpt's config fs, like
nitpicker, drivers... The .sculpt file selects the alternative to use
by a simple tag-value notation.
drivers: pc
The supported tags are as follows.
*Optional* selection of /config files. If not specified, those files are
omitted, which prompts Sculpt to manage those configurations
automatically or via the Leitzentrale GUI:
fonts
nic_router
event_filter
wifi
runtime
gpu_drv
Selection of mandatory /config files. If not specified, the respective
'default' alternative will be used.
nitpicker
deploy
fb_drv
clipboard
drivers
numlock_remap
leitzentrale
usb
system
ram_fs
Furthermore, the .sculpt file supports the optional selection of
supplemental content such as a set of launchers.
launches: nano3d system_shell
Another type of content are the set of blessed pubkey/download files
used for installing and verifying software on target.
With the new version, it has become possible to supply a depot with the
the system image. The depot content is assembled according to the 'pkg'
attributes found in launcher files and the selected deploy config.
The resulting depot is incorporated into the system image as 'depot.tar'
archive. It can be supplied to the Sculpt system by mounting it into the
ram fs as done by the 'ram_fs/depot' configuration for the ram fs.
It is possible to add additional boot modules to the system image. There
are two options.
build: <list of targets>
This tag prompts the sculpt.run script to build the specified targets
directly using the Genode build system and add the created artifacts
into the system image as boot modules.
import: <list of depot src or pkg archives>
This tag instructs Sculpt to supply the specifid depot-archive content
as boot modules to the system image. This change eliminates the need for
board-specific pkg/sculpt-<board> archives. The board-specific
specializations can now be placed directly into the respective .sculpt
files by using 'import:'.
To make the use of Sculpt as testbed during development more convenient,
the log output of the drivers, leitzentrale, and runtime subsystems
can be redirected to core using the optional 'LOG=core' argument, e.g.,
make run/sculpt KERNEL=linux BOARD=linux LOG=core
The former pkg/sculpt-installation and pkg/sculpt-installation-pc
archives have been replaced by pkg/sculpt_distribution-pc, which
references the generic pkg/sculpt_distribution archive. Those pkgs are
solely used for publishing / distribution purposes.
Fixes #4369
2022-01-06 16:44:51 +00:00
|
|
|
<config arch="">
|
|
|
|
|
|
|
|
|
|
<common_routes>
|
|
|
|
|
<service name="ROM" label_last="ld.lib.so"> <parent/> </service>
|
|
|
|
|
<service name="ROM" label_last="init"> <parent/> </service>
|
|
|
|
|
<service name="CPU"> <parent/> </service>
|
|
|
|
|
<service name="PD"> <parent/> </service>
|
|
|
|
|
<service name="LOG"> <parent/> </service>
|
|
|
|
|
<service name="Timer"> <parent/> </service>
|
|
|
|
|
</common_routes>
|
|
|
|
|
|
|
|
|
|
<start name="recall_fs" pkg="chroot">
|
|
|
|
|
<route>
|
|
|
|
|
<service name="File_system"> <child name="default_fs_rw"/> </service>
|
|
|
|
|
</route>
|
|
|
|
|
<config> <default-policy path_prefix="/recall" writeable="yes"/> </config>
|
|
|
|
|
</start>
|
|
|
|
|
|
|
|
|
|
<start name="wm" pkg="wm">
|
|
|
|
|
<route>
|
2022-04-13 10:31:57 +00:00
|
|
|
<service name="ROM" label_last="clipboard"> <parent/> </service>
|
|
|
|
|
<service name="Report" label_last="clipboard"> <parent/> </service>
|
|
|
|
|
<service name="Report" label_last="shape"> <parent label="shape"/> </service>
|
|
|
|
|
<service name="Gui" label="focus"> <parent label="focus"/> </service>
|
|
|
|
|
<service name="Gui"> <parent/> </service>
|
Modularize Sculpt OS image creation
This patch equips Sculpt with the ability to customize the system image
in very flexible ways.
All customizable aspects of the image have been relocated from the
former sculpt.run script and the accompanied gems/run/sculpt/ directory
to a new location - the sculpt/ directory - which can exist in any
repository. The directory at repos/gems/sculpt/ serves as reference.
The sculpt directory can host any number of <name>-<board>.sculpt files,
each containing a list of ingredients to be incorporated into the
Sculpt system image. The <name> can be specified to the sculpt.run
script. E.g., the following command refers to the 'default-pc.sculpt'
file:
make run/sculpt KERNEL=nova BOARD=pc SCULPT=default
If no 'SCULPT' argument is supplied, the value 'default' is used.
A .sculpt file refers to a selection of files found at various
subdirectries named after their respective purpose. In particular, There
exists a subdirectory for each file in Sculpt's config fs, like
nitpicker, drivers... The .sculpt file selects the alternative to use
by a simple tag-value notation.
drivers: pc
The supported tags are as follows.
*Optional* selection of /config files. If not specified, those files are
omitted, which prompts Sculpt to manage those configurations
automatically or via the Leitzentrale GUI:
fonts
nic_router
event_filter
wifi
runtime
gpu_drv
Selection of mandatory /config files. If not specified, the respective
'default' alternative will be used.
nitpicker
deploy
fb_drv
clipboard
drivers
numlock_remap
leitzentrale
usb
system
ram_fs
Furthermore, the .sculpt file supports the optional selection of
supplemental content such as a set of launchers.
launches: nano3d system_shell
Another type of content are the set of blessed pubkey/download files
used for installing and verifying software on target.
With the new version, it has become possible to supply a depot with the
the system image. The depot content is assembled according to the 'pkg'
attributes found in launcher files and the selected deploy config.
The resulting depot is incorporated into the system image as 'depot.tar'
archive. It can be supplied to the Sculpt system by mounting it into the
ram fs as done by the 'ram_fs/depot' configuration for the ram fs.
It is possible to add additional boot modules to the system image. There
are two options.
build: <list of targets>
This tag prompts the sculpt.run script to build the specified targets
directly using the Genode build system and add the created artifacts
into the system image as boot modules.
import: <list of depot src or pkg archives>
This tag instructs Sculpt to supply the specifid depot-archive content
as boot modules to the system image. This change eliminates the need for
board-specific pkg/sculpt-<board> archives. The board-specific
specializations can now be placed directly into the respective .sculpt
files by using 'import:'.
To make the use of Sculpt as testbed during development more convenient,
the log output of the drivers, leitzentrale, and runtime subsystems
can be redirected to core using the optional 'LOG=core' argument, e.g.,
make run/sculpt KERNEL=linux BOARD=linux LOG=core
The former pkg/sculpt-installation and pkg/sculpt-installation-pc
archives have been replaced by pkg/sculpt_distribution-pc, which
references the generic pkg/sculpt_distribution archive. Those pkgs are
solely used for publishing / distribution purposes.
Fixes #4369
2022-01-06 16:44:51 +00:00
|
|
|
</route>
|
|
|
|
|
</start>
|
|
|
|
|
|
|
|
|
|
<start name="window_layouter" pkg="window_layouter">
|
|
|
|
|
<route>
|
|
|
|
|
<service name="ROM" label="window_list"> <child name="wm"/> </service>
|
|
|
|
|
<service name="ROM" label="focus_request"> <child name="wm"/> </service>
|
|
|
|
|
<service name="ROM" label="hover"> <child name="wm"/> </service>
|
|
|
|
|
<service name="ROM" label="decorator_margins"> <child name="wm"/> </service>
|
|
|
|
|
<service name="ROM" label="rules"> <child name="wm"/> </service>
|
|
|
|
|
<service name="Report"> <child name="wm"/> </service>
|
|
|
|
|
<service name="Gui"> <child name="wm"/> </service>
|
|
|
|
|
<service name="File_system" label="recall"> <child name="recall_fs"/> </service>
|
|
|
|
|
</route>
|
|
|
|
|
</start>
|
|
|
|
|
|
|
|
|
|
<start name="themed_decorator" pkg="themed_decorator">
|
|
|
|
|
<route>
|
|
|
|
|
<service name="ROM" label="window_layout"> <child name="wm"/> </service>
|
|
|
|
|
<service name="ROM" label="pointer"> <child name="wm"/> </service>
|
|
|
|
|
<service name="Report"> <child name="wm"/> </service>
|
|
|
|
|
<service name="Gui"> <child name="wm"/> </service>
|
|
|
|
|
</route>
|
|
|
|
|
</start>
|
|
|
|
|
|
|
|
|
|
<start name="fonts_fs" pkg="fonts_fs">
|
|
|
|
|
<route>
|
|
|
|
|
<service name="ROM" label="config">
|
|
|
|
|
<parent label="config -> managed/fonts"/> </service>
|
|
|
|
|
</route>
|
|
|
|
|
</start>
|
|
|
|
|
|
|
|
|
|
<start name="sticks_blue_backdrop"/>
|
|
|
|
|
<start name="nano3d"/>
|
|
|
|
|
<start name="system_shell"/>
|
|
|
|
|
|
|
|
|
|
</config>
|
