Version 60 (modified by 16 years ago) ( diff ) | ,
---|
Linux build instructions
While we try to not favor any distribution, we only build with certain distributions. This includes Debian, Ubuntu, Gentoo and Red Hat Enterprise Linux. Things should not be much different for other distributions though. If you want to supply specific build instructions (especially package names) for other distributions, please contact the VirtualBox team.
Prerequisites
You need:
- GCC 3.3.3 or later (except for the GCC 4.0.x series). GCC 4.3.3 is recommended.
- as86 (real mode assembler, usually part of the dev86 or bin86 package.)
- bcc (Bruce Evans C Compiler; often part of the dev86 package)
Note: The bcc compiler contained in openSUSE10.2 as part of dev86-0.16.0-218 is known to generate broken code. Unfortunately, bcc -v is not supported. - IASL (Intel ACPI compiler)
- xsltproc (libxslt, XML style sheet processor)
- libxerces (only VBox version < 1.6, Xerces XML parser; the C++, not the Java version!)
- libxalan (only VBox version < 1.6, Xalan XSL library, depends on Xerces; again, the C++, not the Java version!)
- libxml2 (only VBox version >= 1.6, XML file handling)
- libxslt1 (only VBox version >= 1.6, XML file transformation)
- libXcursor (required to support color mouse pointers in guest)
- Qt 3.3.x (with x >= 5 if possible; only for VBox version <= 2.2.0)
- Qt 4.4.x (with x >= 3)
- libIDL
- libSDL
- ALSA (audio backend)
- PulseAudio (audio backend)
- libhal (detect host floppy/DVD)
- libcap (CAP_NET_RAW for ICMP sockets in NAT)
- python2.5 (Python bindings)
- gsoap (webservice API, 2.7.9f or higher)
- Xmu (for OpenGL)
- Mesa (for OpenGL)
On 64-bit systems you need the following packages as well:
- ia32-libs (various libraries needed for compiling the 32-bit guest additions)
- libc6-dev-i386 (libc6 i386 development headers)
- lib32gcc1 (gcc support for i386)
- gcc-multilib (gcc support for i386)
- lib32stdc++6 (libstdc++ for i386)
- g++-multilib (g++ support for i386)
On Debian-based systems, the following command should install the required packages:
- for VBox version < 1.6:
apt-get install gcc g++ bcc iasl xsltproc xalan libxalan110-dev uuid-dev \ zlib1g-dev libidl-dev libsdl1.2-dev libxcursor-dev \ libqt3-headers libqt3-mt-dev libasound2-dev libstdc++5 \ libhal-dev libpulse-dev linux-kernel-headers
- for VBox version >= 1.6 and version < 2.2:
apt-get install gcc g++ bcc iasl xsltproc uuid-dev zlib1g-dev libidl-dev \ libsdl1.2-dev libxcursor-dev libqt3-headers libqt3-mt-dev \ libasound2-dev libstdc++5 libhal-dev libpulse-dev libxml2-dev \ libxslt1-dev python2.5-dev libqt4-dev qt4-dev-tools libcap-dev \ linux-kernel-headers
- for VBox version >= 2.2:
apt-get install gcc g++ bcc iasl xsltproc uuid-dev zlib1g-dev libidl-dev \ libsdl1.2-dev libxcursor-dev libasound2-dev libstdc++5 \ libhal-dev libpulse-dev libxml2-dev libxslt1-dev \ python2.5-dev libqt4-dev qt4-dev-tools libcap-dev \ libxmu-dev mesa-common-dev libglu1-mesa-dev \ linux-kernel-headers
On 64-bit Debian-based systems, the following command should install the required additional packages:
apt-get install ia32-libs libc6-dev-i386 lib32gcc1 gcc-multilib \ lib32stdc++6 g++-multilib
On Gentoo, the following should do:
emerge -av sys-devel/bin86 sys-devel/dev86 sys-power/iasl libxslt xerces-c \ xalan-c libXcursor =qt-3* libIDL libsdl hal alsa-lib pulseaudio
Note that VirtualBox makes use of YASM as its assembler which is part of the source repository as the currently available releases of YASM contain various bugs. As soon as a working release becomes officially available, we will add YASM to the list of prerequisites.
Building on a 64bit host still requires 32bit libraries and build tools as the Guest Additions which are part of the build process are 32bit. Note that on 64bit Ubuntu systems some links to shared libraries are missing. This can be fixed with
ln -s libX11.so.6 /usr/lib32/libX11.so ln -s libXTrap.so.6 /usr/lib32/libXTrap.so ln -s libXt.so.6 /usr/lib32/libXt.so ln -s libXtst.so.6 /usr/lib32/libXtst.so ln -s libXmu.so.6 /usr/lib32/libXmu.so ln -s libXext.so.6 /usr/lib32/libXext.so
Building VirtualBox
- 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 calledenv.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.
- 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
- To build a release package, type
kmk all
This produces the required binaries inout/linux.x86/release/bin/
. If you want to build a debug version, typekmk BUILD_TYPE=debug
In case you have more than one CPU core, kmk will automatically do a parallel build.
- If you made a hardened build (that is, you omitted the --disable-hardened switch from configure) you have to set some symbolic links manually to be able to start VMs from the bin/ directory:
cd out/linux.x86/release/bin/components ln -s ../VBoxDDU.so . ln -s ../VBoxREM.so . ln -s ../VBoxRT.so . ln -s ../VBoxVMM.so . ln -s ../VBoxXPCOM.so .
Building OSE packages for distribution
Never disable hardening (see previous section) when creating packages for redistribution.
To be more LSB-compliant, change the default pathes which are used by the VirtualBox binaries to find their components. Add the following build variables to LocalConfig.kmk:
- VBOX_PATH_APP_PRIVATE_ARCH := /usr/lib/virtualbox
- This is the application's private directory, architecture-dependent.
- VBOX_PATH_SHARED_LIBS := $(VBOX_PATH_APP_PRIVATE_ARCH)
- Where to put the shared libraries, usually the same directory as the private path as the VirtualBox shared libraries are normally not used by any other application.
- VBOX_WITH_ORIGIN :=
- Disable RPATH=$ORIGIN and use a fixed RUNPATH.
- VBOX_WITH_RUNPATH := $(VBOX_PATH_APP_PRIVATE_ARCH)
- Set RUNPATH to the directory where our shared libraries can be found.
- VBOX_PATH_APP_PRIVATE := /usr/share/virtualbox
- This is the applications's private directory, not architecture-dependent.
- VBOX_PATH_APP_DOCS := /usr/share/doc/virtualbox
- Set the directory containing the documentation. The file VirtualBox.chm and UserManual.pdf (both are not part of the OSE distribution) are searched within this directory.
- VBOX_WITH_TESTCASES :=
- Save compile time by not building the testcases.
- VBOX_WITH_TESTSUITE :=
- Save compile time by not building the testsuite.
Running your build
You can run VirtualBox directly from the build target directory (out/linux.x86/release/bin/
). But first of all, you must build and install the VirtualBox kernel module, whose sources will have been copied to the build target directory.
So, issue the following:
cd out/linux.x86/release/bin/src make sudo make install cd ..
Then it should have been installed to your modules directory and you can load it using modprobe vboxdrv
. Make sure you give yourself read and write access to /dev/vboxdrv
.
Finally, you can start one of the frontends, e.g.
LD_LIBRARY_PATH=. ./VirtualBox
Note that the LD_LIBRARY_PATH=.
is required for VBox version < 2.0 because we have to find our .so
files and the output directory is not in the system's library path. Starting with VBox 2.0, the binaries have RPATH set.