[vbox-dev] Windows build status
rudolfs.bundulis at gmail.com
Sat Oct 18 14:15:59 UTC 2014
since the hardening has been introduced it seems that I can't host a VM
inside my process that provides the UI frontend. I saw a confirmation on
this in the VirtualBox forum
https://forums.virtualbox.org/viewtopic.php?f=34&t=62837 and the suggestion
was to make your own build and either disable hardening or add the host
process to the process whitelist. So I got together all the dependencies
and started the build setup on Windows but ran into some issues that I'd
like to understand:
1) libSDL - the version avaible on the page 1.2.15, has a different library
folder layout than what configure.vbs expects - it has lib\x86 and lib\x64
instead of just lib, but it was trivial to fix the .vbs file
2) curl - at this point there are no VC devel builds on the homepage so I
assume I need to build curl from sources with VS2010?
3) Customization - it seems that configure.vbs wants all the components
(SDL, QT - which takes time to build, ...), but since I don't need any of
the frontends, is there any how I can actually build without these
components? I looked at the Config.kmk and there are a lot of variables to
play around, but what I wanted to understand is if I can do this without
leaving out the whole configure.vbs part.
4) Studio support - I'ts not an issue to use VS2010 for me, but since my
project is on VS2013 I wanted to know, what are the main risks if I just
try to patch the configure.vbs with the paths for VS2013? I would assume
ATL could containt changes, but what else?
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the vbox-dev