1 Departure
2 =========
3
4 This is a collection of L4Re packages for providing and using filesystems and
5 related components.
6
7 This directory (departure) should be installed within the pkg directory in the
8 L4Re distribution.
9
10 Building Fiasco and L4Re
11 ------------------------
12
13 Although this is generally documented, the concise instructions for building
14 the software have not been preserved in the L4Re distribution, requiring the
15 perusal of online resources. For example:
16
17 https://github.com/kernkonzept/manifest/wiki/BUILDING
18
19 Some reminders are provided below to save the reader the bother of looking up
20 or searching for this information, particularly if it does not continue to
21 reside in the above location.
22
23 First of all, the ham tool has to be obtained. This can be done as follows:
24
25 git clone https://github.com/kernkonzept/ham.git
26
27 It can be built as follows:
28
29 cd ham
30 make
31
32 Returning to the parent directory, the Fiasco and L4Re distributions can be
33 obtained as follows:
34
35 ham/ham init -u https://github.com/kernkonzept/manifest.git
36 ham/ham sync
37
38 (Referencing ham within its repository avoids any need to put the program on
39 the PATH, which is largely unnecessary since we will only be using it in this
40 particular location and for the specific purpose of downloading the remaining
41 software of interest.)
42
43 Here is a quick summary of the build process for Fiasco starting at the parent
44 directory of the Fiasco and L4Re distributions:
45
46 cd fiasco
47 make BUILDDIR=mybuild
48 cd mybuild
49 make config
50 make
51
52 The final make command can employ flags such as "-j8" or even "-j" without any
53 parameter to parallelise the build.
54
55 At this point, this directory (departure) can be copied into the L4Re
56 distribution within the pkg directory.
57
58 Here is a quick summary of the build process for L4Re, also starting at the
59 parent directory of the Fiasco and L4Re distributions:
60
61 cd l4
62 make B=mybuild
63 make O=mybuild config
64 make O=mybuild
65
66 Again, the final make command can employ parallelisation flags. For example:
67
68 make -j8 O=mybuild
69
70 Along with the usual L4Re software, this will also build the software provided
71 by this distribution if it has been copied into the pkg/departure location
72 within the l4 directory.
73
74 Running Programs from this Distribution
75 ---------------------------------------
76
77 To make the test programs available to L4Re, add the following line to the
78 L4Re conf/Makeconf.boot file:
79
80 MODULE_SEARCH_PATH += $(L4DIR_ABS)/pkg/departure/conf
81
82 It may also be necessary to add the following line as well:
83
84 BOOTSTRAP_SEARCH_PATH += $(L4DIR_ABS)/pkg/departure/conf
85
86 This removes any need to copy program configuration files and associated
87 resources to the L4Re distribution itself.
88
89 The program module lists in the conf subdirectory can either be appended to
90 the L4Re conf/modules.list file, or a specific .list file can be copied to the
91 conf/modules.list location (potentially after taking a backup copy of the
92 original file).