Changes between Version 35 and Version 36 of Linux build instructions

Timestamp:

Feb 15, 2008 11:26:37 AM (16 years ago)

Author:

Frank Mehnert

Comment:

--

Linux build instructions

@@ -98 +98 @@
 ./configure
 }}}
-If it finds everything it needs, it will create a file called '!AutoConfig.kmk' containing paths to the various tools on your system. Also, it will create an environment setup script called `env.sh`.  This step only has to be done once (if something changes in your build tool setup, you might have to repeat it but keep in mind that both output files will be overwritten).
+ If it finds everything it needs, it will create a file called '!AutoConfig.kmk' containing paths to the various tools on your system. Also, it will create an environment setup script called `env.sh`.  This step only has to be done once (if something changes in your build tool setup, you might have to repeat it but keep in mind that both output files will be overwritten).
 
  2. Whenever you want to build !VirtualBox, you have to open a shell and source the generated environment setup script 'env.sh', i.e. do
@@ -105 +105 @@
 }}}
 
- 3. To build a release package, type `kmk all`. This produces the required binaries in `out/linux.x86/release/bin/`. (If you want to build a debug version, type `kmk BUILD_TYPE=debug`.) In case you have more than one CPU core, you could take advantage of our parallel build system by supplying `-j3` (number of cores + 1) as an option to kmk.
+ 3. To build a release package, type
+{{{
+kmk all
+}}}
+ This produces the required binaries in `out/linux.x86/release/bin/`. If you want to build a debug version, type
+{{{
+kmk BUILD_TYPE=debug
+}}}
+ In case you have more than one CPU core, you could take advantage of our parallel build system by supplying `-j3` (number of cores + 1) as an option to kmk.