[vbox-dev] Help building VBox on WinXP - understanding toolchain
biteme at bitbasher.net
Tue Mar 25 22:55:06 PDT 2008
Heya thanks for that link! I'll download and try it out.
It looks like I have to first compile QT/win before I can use it as a tool for
VBox, but the QT build instructions don't look too weird. Hopefully this will
I'm going to try out qt 3.3.5-5 as it seems about the right time. If you've
got this to work and if you used a different qt version please let me know
just in case 3.3.5-5 doesn't work well.
In article <47E8BC6A.80308 at sun.com>, Andreas.L at Sun.COM
>there is a free implementation of Qt/win 3.3.x as Open Source, based on
>the last Trolltech's Qt/x11 3.3.x branch, which is also Open Source.
>Using this package, it is possible to find Qt with the "configure.vbs"
>script and compile the VirtualBox frontend.
>Take a look here: http://qtwin.sourceforge.net/
>> Well, I worked with this for 1.5 days on the weekend and I've concluded
>> the average developer cannot build VirtualBox for Windows.
>> I got all the tools installed that are listed in the prerequisites and
>> configure.vbs finds them all. Then configure.vbs ABORTS because of QT.
>> It appears (to me) that VirtualBox uses an older (and now unavailable)
>> proprietary version of QT/win 3.3.x but the current publicly available
>> versions of QT are version 4.x and greater.
>> It seems that VirtualBox is not compatible with QT 4.x and only works with
>> not-available QT 3.3.x versions.
>> I did ready the section in the build instructions about the issue with QT.
>> first I didn't understand the problem (because the documentation was
>> by a developer who was VERY familiar with the tools). After doing a bit of
>> internet snooping it seems that the TOOLS NEEDED TO BUILD VIRTUALBOX FOR
>> WINDOWS ARE NOT AVAILABLE. Please correct me if I'm wrong, but I cannot
>> any versions of QT 3.3.x that VirtualBox needs to work.
>> So now the question becomes, is it even possible for someone other than
>> Innotek/Sun to build VBox for Windows if they haven't purchased the QT
>> toolkit? Also note that Trolltech no longer supports QT versions < 4.0.
>> In article <F6258B02585E474B97BDF70C70B840DC at DavidLaptop>,
>> mykeysdavid at gmail.com says...
>>> If you plan using MinGW only for VirtualBox, then there are folders that
>>> be used.
>>> Go to the root VirtualBox directory, then go to "tools/win.x86". Here you
>>> create the following directory structure, in addition of the already
>>> existing directories.
>>> ---(all the files of MinGW except the Win32 API stuff)
>>> ---(The win32 API stuff)
>>> Then you run again the configure.vbs script and it should detect MinGW
>>> without any supplemental configuration.
>>> From: "Doug" <biteme at bitbasher.net>
>>> Sent: Saturday, March 22, 2008 12:58 AM
>>> To: <vbox-dev at virtualbox.org>
>>> Subject: [vbox-dev] Help building VBox on WinXP - understanding toolchain
>>>> I've read the information about building vbox on windows here:
>>>> I have no trouble installing all the native Win32 tools (VS2005, SDK,
>>>> DDK, SDL, DXSDK), but the MinGW tools are all just a bunch of files in
>>>> tar archives.
>>>> Where do I install all the MinGW files? Do I need to set them up in any
>>>> special way or run any installer?
>>>> There is mention on the page of cygwin but cygwin is NOT listed as a
>>>> prerequisite tool. Do I need cygwin? If so, where do I get it and
>>>> which version should I use.
>>>> Basically, if someone can give me a few easy steps to get all the needed
>>>> tools correctly installed for WinXP I'd really appreciate it.
>>>> vbox-dev mailing list
>>>> vbox-dev at virtualbox.org
>> vbox-dev mailing list
>> vbox-dev at virtualbox.org
>System Software Engineer, VirtualBox
>Sun Microsystems GmbH
>71384 Weinstadt, Germany
>phone: +49 7151 604050
>Sitz der Gesellschaft: Sun Microsystems GmbH,
>Sonnenallee 1, 85551 Kirchheim-Heimstetten
>Amtsgericht Muenchen: HRB 161028
>Geschaeftsfuehrer: Thomas Schroeder,
>Wolfgang Engels, Dr. Roland Boehmer
>Vorsitzender des Aufsichtsrates: Martin Haering
More information about the vbox-dev