virtualbox.org

I'm currently trying to build it, and I encoutered a lot of problems and bugs, and I'm not sure to be successful in the end.

So I'd like to share experience with others...
Is there a FAQ, a tutorial etc...

Why people do not distribute the binaries they built ?

Karl

Here are some tips/bugs/work-arounds I encountered :

- a lot of default installation paths of required microsoft tools cause problems because they have spaces or others non standards chars. So either install them in simple dirs (e.g d:\visualstudio, or create symbolic links using junction.exe (see sysinternals suite).

- MS Visual Studio 2008 is not supported (as stated in the doc), I tested with the 2003 edition

- run the script Common7\Tools\vsvars32.bat before running the configure.vbs script

- there's a bug in configure.vbs that prevents him from accepting the c++ version :
è bug in configure.vbs around lines 980 : it checks for “Version” instead of “version”
replace line
if (InStr(1, g_strShellOutput, "Version 13.10") <= 0) _
by
if (InStr(1, g_strShellOutput, "version 13.10") <= 0) _

- the options --with-qt3 as output by configure.vbs --help does not exist. It is actually --with-qt

- to get rid of the xerces requirement use the --internal option

- I used all the --with options, so for my example my final cmd line is :
cscript configure.vbs --with-VC=d:\VS\vc7 --with-SDK=d:\MSDK
--with-DXSDK=d:\DXSDK --with-libSDL=d:\SDL-1.2.13 --internal --with-qt=d:\qt-3.
3.x-p8

- bug : the env.bat does not work, it looks for "env.cmd" in tools that does not exist

At this point, when I cd into the src/ dir, qnd type kmk, I get :
Makefile.kmk:38: D:/VirtualBox-2.0.0/src/VBox/Devices/Storage/VBoxHDDFormats/Makefile.kmk: No such file or directory
Makefile.kmk:41: D:/VirtualBox-2.0.0/src/VBox/Devices/PC/PXE/Makefile.kmk: No su
ch file or directory

and there's no VBoxHDDFormats dir in D:/VirtualBox-2.0.0/src/VBox/Devices/Storage, so I'm stuck here....

Sorry, the Makefiles for the Windows OSE version are not in a very good shape currently. OSE for Linux should build fine. Btw, 2.0.2 was released three days ago.

Regarding the missing Makefile: You have to define VBOX_OSE in your LocalConfig.kmk. The configure.vbs script (which is the preferred way for start building VBox) should do this already.

Ok, I've set VBOX_OSE=1 in the toplevel Config.kmk file.
And it started compiling (neat progress).
But soon it fails :

Code: Select all

D:/MSDK\Include\specstrings.h(9) : fatal error C1083: Impossible d'ouvrir le fic
hier include : 'sal.h' : No such file or directory
kmk.exe[1]: *** [D:/VirtualBox-2.0.0/out/win.x86/release/obj/src/VBox/Runtime/Ru
ntimeR3/r3/alloc-ef.obj] Error 2
The failing command:
        @ D:/VS/Vc7/bin/cl.exe -c -TP -c -nologo -O2 -Zi -Zl -GR- -GX- -GF- -MD
-W3 -wd4065 -wd4244 -Ogitb2 -Oy- -ID:/VirtualBox-2.0.0/src/VBox/Runtime/include
-ID:/VirtualBox-2.0.0/src/libs/liblzf-1.51 -ID:/MSDK/Include -ID:/MSDK/Include -
ID:/WINDDK/3790.1830/inc/ddk -ID:/WINDDK/3790.1830/inc/ddk/wnet -ID:/WINDDK/3790
.1830/inc/wnet -ID:/WINDDK/3790.1830/inc/ddk/wdm/wnet -ID:/VirtualBox-2.0.0/incl
ude -ID:/VirtualBox-2.0.0/out/win.x86/release -ID:/VS/Vc7/include -ID:/VS/Vc7/at
lmfc/include -DVBOX -DVBOX_OSE -DVBOX_WITH_INTERNAL_NETWORKING -DRT_OS_WINDOWS -
D__WIN__ -DRT_ARCH_X86 -D__X86__ -D__WIN32__ -D_X86_ -DIN_RING3 -DHC_ARCH_BITS=3
2 -DGC_ARCH_BITS=32 -DIN_RT_R3 -DIN_SUP_R3 -DLDR_WITH_NATIVE -DLDR_WITH_ELF32 -D
LDR_WITH_PE -DRT_WITH_VBOX -FdD:/VirtualBox-2.0.0/out/win.x86/release/obj/src/VB
ox/Runtime/RuntimeR3/r3/alloc-ef-obj.pdb -FD -FoD:/VirtualBox-2.0.0/out/win.x86/
release/obj/src/VBox/Runtime/RuntimeR3/r3/alloc-ef.obj D:\\VirtualBox-2.0.0\\src
\\VBox\\Runtime\\r3\\alloc-ef.cpp
kmk.exe[1]: Leaving directory `D:/VirtualBox-2.0.0/src/VBox/Runtime'
kmk: *** [pass_libraries_before] Error 2

karl,

Sal.h is an include file in the platform SDK IIRC. Also, if you changed your config.kmk file at all, make sure to do a kmk clean first to clean the dist

Also, I think you might need VS2005 in order to compile now. I know a few of the modules use newer calls that are only available in VS2005 SP1.

Also as a note, if you use --internal, that's when the env.bat is incorrect. When actually pointing to both X's, it generates an appropriate env.bat (still would like to know the impact of using --internal).

The only thing I saw was for VirtualBox3, it's looking for vboxqt-mt.dll instead of qt-mt.dll. In my case I just copied the main dll over and then it worked fine.

I downloaded the latest snapshot last night and compiled it OK using Vstudio 2005 SP1 Team edition

Thanks a lot, I'll try to get a VS 2005 edition.

Can I get your binary ? Or more generally could you share your binary with the rest of the world ?

I mean are there legal reasons that forbid doing this ?

Thanks again

I'll have to check a few things with our internal licensing but I don't know why I couldn't (QT's license might be a bit odd for QT4, that's the only thing I'm thinking)

Aren't you using the QT open source edition ?

not for 4 i'm not... we have a license here where I work..

I'll see about downloading 4 opensource and see if that'll compile it just fine, i know on 3 there was issues

Great !! in the meantime I'll try to get the MS VS 2005.

any news ?

not yet.... haven't had a chance to recompile Qt yet.

the latest patches for VS compile are for 4.3.5 so I have to get that ready first.

virtualbox.org

Does anyone has sucessfully built the OSE 2.0.0 version ?

Does anyone has sucessfully built the OSE 2.0.0 version ?