Hi Doug, regarding the zlib: The zlib 1.2.1 should be downloaded automatically when you checkout the VBox OSE sources from SVN. Take a look at <VBoxRoot>/src/libs/zlib-1.2.1/. This should be sufficient for all modules. If not, please post the lines with the error of the build log here.
Hope this helps, -Andreas. Doug wrote: > Thanks Andreas for all your help. > > I was able to get the free qt/win 3.3.8 to build. I had to edit > configure.vbs > because it was looking for qt-mt33* but the file I built is named qt-mt3* so > I > changed configure.vbs to only search for one "3" characters not two. I used > the --with-qt=path to locate my qt install/build folder. > > After building qt/win 3.3.8, I also "cheated" and copied everything in qt/lib > to qt/lib/dynamic as that is where vbox looks for qt-mt3.lib. When I build > qt/win 3.3.8 it does not create a "dynamic" folder in the "lib" folder. If > the lib\dynamic folder does not exist with qt files, then configure.vbs will > not find the qt stuff. > > I am current building vbox ose 1.5.6, so perhaps some of my limitations above > are no longer an issue with the current SVN build. > > > A few other minor issues I came across... > > 1. One of vbox's tools requires zlib1.dll. This is not documented in the > prerequisites section of the win32 build documentation. I just downloaded > zlib1.dll and placed it on my path and the tool then worked. > > 2. The win32 build documentation states that I can use either the latest > Windows Platform SDK or one that comes with Visual C++ (in my case, Visual > Studio 2005 Pro). So I used the one that comes with VS2005, but the vbox > build then fails because it cannot find "MIDL" and "MC" in the SDK\bin path. > I solved this problem by copying these tools from my VC2005 bin folder over > to > the SDK\bin folder and then vbox found those tools. > > > After all that I was able to get vbox 1.5.6 to build to completion under > win32 > (YAY!). I haven't tried running it yet, but I think my next goal is to retry > this with the current SVN build. > > Doug. > > > > In article <[EMAIL PROTECTED]>, [EMAIL PROTECTED] > says... > >> Hi Doug, >> >> with the latest sources you now should be able to use Qt/free stuff with >> the VBox Qt frontends. >> Just put the package under "<VBoxRoot>/tools/win.x86/qt/v3.3.3", compile >> Qt/free from there and >> execute "cscript "configure.vbs" again. If you have put Qt/free in >> another location, >> you can use the "--with-qt=<Path>" parameter as well. >> >> Additionally, take a look at http://virtualbox.org/wiki/Build_instructions >> There I've added the required steps in detail on how to build and use >> Qt/free with VBox. >> >> Hope this helps, >> >> -Andreas. >> >> >> Doug wrote: >> >>> Well I was able to build the QT stuff, but the results to NOT match what >>> > vbox > >>> configure.vbs is looking for. >>> >>> Sbox is looking for a few files. Some are found and some are NOT, like: >>> lib/dynamic/qtmain.lib >>> lib/dynamic/qt-mt33*.lib >>> >>> The qt library I built does NOT contain the dynamic folder in lib. Also, I >>> > do > >>> not have a qt-mt33*.lib file, just a qt-mt3.lib file in the lib parent >>> > folder. > >>> I'm not sure what weird version of QT the Innotek was using, but the one I >>> downloaded and built does NOT match the requirements of vbox's >>> > configure.vbs > >>> file. I'm not sure if editing the vbs file will help or if the qt version >>> > I > >>> downloaded is NOT compatible with vbox. >>> >>> Any sugestions? >>> Thanks, >>> Doug. >>> >>> >>> >>> In article <[EMAIL PROTECTED]>, >>> [EMAIL PROTECTED] says... >>> >>> >>>> 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 >>> >>> >>>> work. >>>> >>>> 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. >>>> >>>> Thanks!!! >>>> Doug. >>>> >>>> >>>> In article <[EMAIL PROTECTED]>, >>>> >>>> >>> [EMAIL PROTECTED] >>> >>> >>>> says... >>>> >>>> >>>>> Hi Doug, >>>>> >>>>> 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/ >>>>> >>>>> Regards, >>>>> Andreas >>>>> >>>>> >>>>> >>>>> Doug wrote: >>>>> >>>>> >>>>>> Well, I worked with this for 1.5 days on the weekend and I've concluded >>>>>> >>>>>> >>>> that >>>> >>>> >>>>>> 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 > >>>>>> >>>>>> >>>> the >>>> >>>> >>>>>> not-available QT 3.3.x versions. >>>>>> >>>>>> I did ready the section in the build instructions about the issue with >>>>>> > QT. > >>>>>> >>>>>> >>> >>> >>> >>>> At >>>> >>>> >>>>>> first I didn't understand the problem (because the documentation was >>>>>> >>>>>> >>>> written >>>> >>>> >>>>>> 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 >>>>>> >>>>>> >>>> find >>>> >>>> >>>>>> 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 >>>>>> >>>>>> >>>> 3.3.x >>>> >>>> >>>>>> toolkit? Also note that Trolltech no longer supports QT versions < 4.0. >>>>>> >>>>>> Doug. >>>>>> >>>>>> >>>>>> >>>>>> In article <[EMAIL PROTECTED]>, >>>>>> [EMAIL PROTECTED] says... >>>>>> >>>>>> >>>>>> >>>>>>> If you plan using MinGW only for VirtualBox, then there are folders >>>>>>> > that > >>>>>>> >>>>>>> >>>> can >>>> >>>> >>>>>>> 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. >>>>>>> >>>>>>> win.x86 >>>>>>> -mingw32 >>>>>>> --v3.3.3 >>>>>>> ---(all the files of MinGW except the Win32 API stuff) >>>>>>> -w32api >>>>>>> --v2.5 >>>>>>> ---(The win32 API stuff) >>>>>>> >>>>>>> Then you run again the configure.vbs script and it should detect MinGW >>>>>>> without any supplemental configuration. >>>>>>> >>>>>>> -------------------------------------------------- >>>>>>> From: "Doug" <[EMAIL PROTECTED]> >>>>>>> Sent: Saturday, March 22, 2008 12:58 AM >>>>>>> To: <[email protected]> >>>>>>> Subject: [vbox-dev] Help building VBox on WinXP - understanding >>>>>>> > toolchain > >>>>>>> >>>>>>> >>>>>>> >>>>>>>> Hi, >>>>>>>> >>>>>>>> I've read the information about building vbox on windows here: >>>>>>>> http://www.virtualbox.org/wiki/Windows%20build%20instructions >>>>>>>> >>>>>>>> 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. >>>>>>>> >>>>>>>> Doug. >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> vbox-dev mailing list >>>>>>>> [email protected] >>>>>>>> http://vbox.innotek.de/mailman/listinfo/vbox-dev >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>> _______________________________________________ >>>>>> vbox-dev mailing list >>>>>> [email protected] >>>>>> http://vbox.innotek.de/mailman/listinfo/vbox-dev >>>>>> >>>>>> >>>>>> >>>> >>>> >>> ______________________________________________ >>> vbox-dev mailing list >>> [email protected] >>> http://vbox.innotek.de/mailman/listinfo/vbox-dev >>> >>> > > > > _______________________________________________ > vbox-dev mailing list > [email protected] > http://vbox.innotek.de/mailman/listinfo/vbox-dev > _______________________________________________ vbox-dev mailing list [email protected] http://vbox.innotek.de/mailman/listinfo/vbox-dev
