ehmry/genode
ehmry
/
genode
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

doc: adapt getting started to unified builds

This commit is contained in:
Josef Söntgen 2017-12-04 11:40:04 +01:00 committed by Christian Helmuth
parent 58cbd11f6a
commit 3f91f7402d
1 changed files with 23 additions and 15 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

38
doc/getting_started.txt
View File

@ -44,18 +44,23 @@ build directory yet. For a quick start, let us create one for the Linux base
platform: platform:
! cd <genode-dir> ! cd <genode-dir>
! ./tool/create_builddir linux_x86 BUILD_DIR=build.lx ! ./tool/create_builddir x86_64
The new build directory is called 'build.lx' and configured for the 'linux_x86' This creates a new build directory for building x86_64 binaries in './build'.
platform. To give Genode a try, build and execute a simple demo scenario via: The build system creates unified binaries that work on the given
architecture independent from the underlying base platform, in this case Linux.
! cd build.lx To give Genode a try, build and execute a simple demo scenario via:
! make run/demo
! cd build/x86_64
! make KERNEL=linux run/demo
By invoking 'make' with the 'run/demo' argument, all components needed by the By invoking 'make' with the 'run/demo' argument, all components needed by the
demo scenario are built and the demo is executed. If you are interested in demo scenario are built and the demo is executed. This includes all components
looking behind the scenes of the demo scenario, please refer to which are implicitly needed by the base platform. The base platform that the
'doc/build_system.txt' and the run script at 'os/run/demo.run'. components will be executed upon on is selected via the 'KERNEL' variable. If
you are interested in looking behind the scenes of the demo scenario, please
refer to 'doc/build_system.txt' and the run script at 'os/run/demo.run'.
Using platforms other than Linux Using platforms other than Linux
@ -91,9 +96,10 @@ downloaded and prepared by invoking:
! ./tool/ports/prepare_port grub2 ! ./tool/ports/prepare_port grub2
Now that the base platform is prepared, the 'create_builddir' tool can be used Now that the base platform is prepared, the 'create_builddir' tool can be used
to create a build directory for your platform of choice by giving the platform to create a build directory for your architecture of choice by giving the
as argument. To see the list of available platforms, execute 'create_builddir' architecture as argument. To see the list of available architecture, execute
with no arguments. 'create_builddir' with no arguments. Note, that not all kernels support all
architectures.
For example, to give the demo scenario a spin on the OKL4 kernel, the following For example, to give the demo scenario a spin on the OKL4 kernel, the following
steps are required: steps are required:
@ -102,13 +108,15 @@ steps are required:
! cd <genode-dir> ! cd <genode-dir>
! ./tool/ports/prepare_port okl4 ! ./tool/ports/prepare_port okl4
# Create a build directory # Create a build directory
! ./tool/create_builddir okl4_x86 BUILD_DIR=build.okl4 ! ./tool/create_builddir x86_32
# Uncomment the following line in 'build.okl4/etc/build.conf' # Uncomment the following line in 'x86_32/etc/build.conf'
! REPOSITORIES += $(GENODE_DIR)/repos/libports ! REPOSITORIES += $(GENODE_DIR)/repos/libports
# Build and execute the demo using Qemu # Build and execute the demo using Qemu
! make -C build.okl4 run/demo ! make -C build/x86_32 KERNEL=okl4 run/demo
The procedure works analogously for the other base platforms. The procedure works analogously for the other base platforms. You can, however,
reuse the already created build directory and skip its creation step if the
architecture matches.
How to proceed with exploring Genode How to proceed with exploring Genode