Changes between Version 15 and Version 16 of FreeBSD build instructions

Timestamp:

Sep 21, 2009 7:05:59 PM (15 years ago)

Author:

aeichner

Comment:

FreeBSD build instructions update

FreeBSD build instructions

@@ -5 +5 @@
 If you like to help out with the FreeBSD port, please join the #vbox-dev irc channel or drop a mail on the development mailing list.
 
-'''Current state:''' the kernel driver needs a substantial effort to get ported, so only people who want to help us getting this changed should think about building !VirtualBox on FreeBSD. In other words: without help from FreeBSD kernel experts who can tell us how to safely allocate physical memory, assign it to user processes and the such there's little point in reporting build issues.
+'''Current state:''' It works quite stable by now for FreeBSD 7.x and 8-CURRENT. There is a port in the FreeBSD ports tree too.
 
 == Prerequisites ==
@@ -23 +23 @@
  * '''xsltproc''' (libxslt, XML style sheet processor)[[BR]]
    => {{{/usr/ports/textproc/libxslt}}}
+ * '''libxml2''' [[BR]]
+   => {{{/usr/ports/textproc/libxml2}}}
  * '''libXcursor''' (required to support color mouse pointers in guest) [[BR]]
    => Probably installed, if not try {{{/usr/ports/x11/libXcursor}}}.
@@ -31 +33 @@
  * '''libSDL''' [[BR]]
    => {{{/usr/ports/devel/sdl12}}}
- * '''mkisofs''' [[BR]]
+ * '''mkisofs''' (required only for additions which aren't supported yet) [[BR]]
    => {{{/usr/ports/sysutils/cdrtools}}}
- * '''FreeBSD 6.x compat libs''' for kBuild and other prebuilt binaries [[BR]]
-   => {{{/usr/ports/misc/compat6x}}}
+ * '''kBuild''' (The one provided with the VirtualBox sources doesn't with FreeBSD 8-CURRENT) [[BR]]
+   => {{{/usr/ports/devel/kBuild}}}
+ * '''curl''' [[BR]]
+   => {{{/usr/ports/ftp/curl}}}
+ * '''libXmu''' [[BR]]
+   => {{{/usr/ports/x11-toolkits/libXmu}}}
  * '''Qt 4.4.x''' [[BR]]
    => {{{/usr/ports/x11-toolkits/qt4-gui}}}, {{{/usr/ports/net/qt4-network}}}, {{{/usr/ports/devel/qt4-moc}}}, {{{/usr/ports/net/qt4-uic}}}, {{{/usr/ports/net/qt4-rcc}}}   and {{{/usr/ports/net/qt4-linguist}}} ; or configure --disable-qt
@@ -40 +46 @@
 == Building !VirtualBox ==
 
-To be written.
+ 1. Change to the root directory of the sources and execute the configure script:
+{{{
+./configure --disable-hardening
+}}}
+ 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).
+
+ The switch ''--disable-hardening'' should '''not''' be used for building packages for redistribution or for production use.
+
+ 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
+{{{
+source ./env.sh
+}}}
+
+ 3. To build a release package, type
+{{{
+kmk all
+}}}
+ This produces the required binaries in `out/freebsd.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, kmk will automatically do a parallel build.
 
 == Running your build ==
+You can run !VirtualBox directly from the build target directory (`out/freebsd.x86/release/bin/`). 
 
-To be written.
+You have to load the kernel driver first using {{{kldload ./vboxdrv.ko}}} as root. Make sure you give yourself read and write access to {{{/dev/vboxdrv}}}.
+
+If you made a ''hardened build'', make sure that the setuid stubs have the correct permissions:
+{{{
+for f in VirtualBox VBoxHeadless VBoxSDL VBoxBFE VBoxNetDHCP VBoxNetAdpCtl; do
+  chown root.root $f
+  chmod 4511 $f
+done
+}}}
+
+Finally, you can start one of the frontends, e.g.
+{{{
+LD_LIBRARY_PATH=. ./VirtualBox
+}}}