[vbox-dev] Windows OSE compile
phalbert at cox.net
Tue Aug 2 14:43:27 PDT 2011
Any clue or hint where to look? I really don't want to change the
source since I would like to build against SVN.
All I get from MS is you should not use define and use declare instead.
http://support.microsoft.com/kb/815647. I realize this is more than
likely due to the cross compiling but really you compile this code and
it works. What am I missing.
On 08/01/2011 05:27 PM, Perry Halbert wrote:
> I'm using Windows XP-prox86_32, Visual Studio 2005 pro. I have Windows
> 2003 server if you really think this would work better, but from what
> I can tell XP pro Sp3 should work just fine. These are all guest
> installs, not on metal.
> Well I got it to work, sort of. I now get past the include files
> mis-match error by doing the following:
> Install the Windows Server 2003 R2 Platform SDK and register it in
> VS-2005 then install Windows Software Development Kit (SDK) for
> Windows Server 2008 and .NET Framework 3.5, but manually add the exec
> and lib below the 2003 in the VC++ config.
> I could not get it to work with just the 2003 SDK (VBox lbound error -
> I assume it means missing) nor with just the 2008 SDK due to the
> different libs wanted by configure.vbs.
> But now I have a new set of errors referring to the USB. Error below.
> kBuild: Compiling ServicesR0 -
> E:\trunk\src\VBox\Devices\Bus\SrvPciRawR0.cpp(143) : error C2491:
> 'PciRawR0Init' : definition of dllimport function not allowed
> E:\trunk\src\VBox\Devices\Bus\SrvPciRawR0.cpp(158) : error C2491:
> 'PciRawR0Term' : definition of dllimport function not allowed
> E:\trunk\src\VBox\Devices\Bus\SrvPciRawR0.cpp(169) : error C2491:
> 'PciRawR0InitVM' : definition of dllimport function not allowed
> E:\trunk\src\VBox\Devices\Bus\SrvPciRawR0.cpp(194) : error C2491:
> 'PciRawR0TermVM' : definition of dllimport function not allowed
> E:\trunk\src\VBox\Devices\Bus\SrvPciRawR0.cpp(920) : error C2491:
> 'PciRawR0ProcessReq' : definition of dllimport function not allowed
> kmk: ***
> [E:/trunk/out/win.x86/release/obj/ServicesR0/Bus/SrvPciRawR0.obj] Error 2
> The failing command:
> @ C:/PROGRA~1/MICROS~2/VC/bin/cl.exe -c -TP -c -nologo -O2 -Zi -Zl
> -GR- -EHs- -GF -W3 -wd4244 -GS- -wd4996 -Zc:wchar_t- -O2 -GS- -Oy-
> ocrt -IE:/trunk/include -IE:/trunk/out/win.x86/release
> -IC:/PROGRA~1/MICROS~2/VC/atlmfc/include -DVBOX -DVBOX_WITH_DEBUGGER -D
> VBOX_OSE -DVBOX_WITH_64_BITS_GUESTS -DRT_OS_WINDOWS -D__WIN__
> -DRT_ARCH_X86 -D__X86__ -D__WIN32__ -DIN_RING0 -DIN_RING0_AGNOSTIC
> -DIPRT_NO_CRT -DRT_WITH_NOCRT_A
> LIASES -DHC_ARCH_BITS=32 -DGC_ARCH_BITS=64 -DIN_INTNET_R0 -DIN_RT_R0
> -FD -FoE:/trunk/out/
> kmk: ***
> Deleting file
> On 08/01/2011 10:51 AM, Mark Roddy wrote:
>> Oh I agree. My work related interest is only with the kernel mode
>> components and I have had limited success (one driver so far) porting
>> the OSE build environment into the WDK build environment, and by
>> ‘porting’ I mean ‘abandoning’. At the moment this is a science
>> project to evaluate the merits of moving forward with this approach.
>> I keep responding to these threads on this list in the hope that the
>> vbox side will at some point at least comment on the current
>> situation and what they might be doing about it.
>> *From:*Perry Halbert [mailto:phalbert at cox.net]
>> *Sent:* Monday, August 01, 2011 11:47 AM
>> *To:* Mark Roddy
>> *Cc:* vbox-dev at virtualbox.org
>> *Subject:* Re: [vbox-dev] Windows OSE compile
>> Well I have to agree, but this still does not remedy my current
>> situation as the compile fails if VBox does not see the SDK. So back
>> to square one and still wondering what the actual work around is.
>> On 08/01/2011 10:39 AM, Mark Roddy wrote:
>> There is a conflict in the combining of the SDK/Visual Studio toolchain
>> with the WDK toolchain that presents itself, for example, with the
>> errors in intrin.h. These two sets of include files should basically
>> NEVER be combined, as therein lies madness, or at a minimum the editing
>> of standard include files. This is at least partially MSFTs fault for
>> not reconciling their mess of include files into one set that works
>> across their entire third-party exposed development interface, but one
>> also has to question the path vbox seems to have gone down as well. My
>> own suggestion is to abandon the VS/SDK toolchain entirely and stick
>> with the WDK toolchain for the entire windows build environment, as that
>> set of libraries and include files works from user mode down through
>> kernel mode, at the cost of not always current user mode windows UI
>> related support.
>> -----Original Message-----
>> From:vbox-dev-bounces at virtualbox.org
>> <mailto:vbox-dev-bounces at virtualbox.org>
>> [mailto:vbox-dev-bounces at virtualbox.org] On Behalf Of Perry Halbert
>> Sent: Monday, August 01, 2011 11:24 AM
>> To:vbox-dev at virtualbox.org <mailto:vbox-dev at virtualbox.org>
>> Subject: [vbox-dev] Windows OSE compile
>> Trying to compile the Windows OSE version seems to fail no matter
>> version I try. At least back to 2.2.4 which should still have been in
>> the time frame of the posted instructions. I have read references that
>> I should edit intrin.h on Visual Studio 2005, but I find that hard to
>> believe. Is this true? and if so do you have a working copy of this
>> file or patch?
>> Microsoft (R) Windows Script Host Version 5.7 Copyright (C)
>> Corporation. All rights reserved.
>> Shell inheritance test: OK
>> Source path: OK
>> Checking for kBuild...
>> Found kBuild: E:/trunk/kBuild
>> Found kBuild binaries: E:/trunk/kBuild/bin/win.x86 Checking for
>> Windows 2003 DDK, build 3790 or later...
>> Found Windows 2003 DDK: E:/WINDDK/3790.1830 Checking for Visual
>> Found Visual C++ v8 (or later): C:/PROGRA~1/MICROS~2/VC (C:/Program
>> Files/Microsoft Visual Studio 8/VC) Checking for Windows Platform SDK
>> Found Windows Platform SDK: C:/PROGRA~1/MI2578~1/Windows/v6.1
>> (C:/Program Files/Microsoft SDKs/Windows/v6.1) Checking for Midl.exe...
>> Found Midl.exe: C:/PROGRA~1/MI2578~1/Windows/v6.1/bin/Midl.exe
>> (C:/Program Files/Microsoft SDKs/Windows/v6.1/Bin/Midl.exe) Checking for
>> Direct X SDK...
>> Found Direct X SDK: C:/PROGRA~1/MI22C6~1 (C:/Program Files/Microsoft
>> DirectX SDK (October 2006)) Checking for MinGW GCC v3.3.x + Binutils +
>> Runtime + W32API...
>> Found MinGW (GCC v3.3.3): E:/MinGW
>> Found W32API: E:\MinGW
>> Checking for libSDL...
>> Found libSDL: E:/SDL-1.2.14-win32
>> Checking for libxml2...
>> Found libxml2: E:/libxml2-2.7.8.win32
>> Checking for libxslt...
>> Found libxslt: E:/libxslt-1.0.32.win32 Checking for openssl...
>> Found openssl: E:/OpenSSL-Win32
>> Checking for libcurl...
>> Found libcurl: E:/libcurl
>> Checking for Qt4...
>> Found Qt4 : E:/QT4
>> Checking for Python...
>> Found Python : E:\Python27
>> (I also have Gsoap-2.7 installed which works fine and reference in
>> Execute env.bat once before you start to build VBox:
>> C:\PROGRA~1\MICROS~2\VC\include\intrin.h(944) : error C2733:
>> second C
>> linkage of overloaded function '_interlockedbittestandset' not allowed
>> C:\PROGRA~1\MICROS~2\VC\include\intrin.h(944) : see
>> of '_interlockedbittestandset'
>> C:\PROGRA~1\MICROS~2\VC\include\intrin.h(945) : error C2733: second C
>> linkage of overloaded function '_interlockedbittestandreset' not allowed
>> C:\PROGRA~1\MICROS~2\VC\include\intrin.h(945) : see
>> of '_interlockedbittestandreset'
>> kmk: ***
>> [E:/trunk/out/win.x86/release/obj/RuntimeBldProg/r3/alloc-ef.obj] Error
>> vbox-dev mailing list
>> vbox-dev at virtualbox.org <mailto:vbox-dev at virtualbox.org>
> vbox-dev mailing list
> vbox-dev at virtualbox.org
More information about the vbox-dev