<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
@font-face
{font-family:Verdana;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";
color:black;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";
color:black;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";
color:black;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;
color:black;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";
color:black;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body bgcolor=white lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>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.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext'>From:</span></b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext'> Perry Halbert [mailto:phalbert@cox.net] <br><b>Sent:</b> Monday, August 01, 2011 11:47 AM<br><b>To:</b> Mark Roddy<br><b>Cc:</b> vbox-dev@virtualbox.org<br><b>Subject:</b> Re: [vbox-dev] Windows OSE compile<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span style='font-family:"Verdana","sans-serif"'>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.<br><br><br></span><br>On 08/01/2011 10:39 AM, Mark Roddy wrote: <o:p></o:p></p><pre>There is a conflict in the combining of the SDK/Visual Studio toolchain<o:p></o:p></pre><pre>with the WDK toolchain that presents itself, for example, with the<o:p></o:p></pre><pre>errors in intrin.h. These two sets of include files should basically<o:p></o:p></pre><pre>NEVER be combined, as therein lies madness, or at a minimum the editing<o:p></o:p></pre><pre>of standard include files. This is at least partially MSFTs fault for<o:p></o:p></pre><pre>not reconciling their mess of include files into one set that works<o:p></o:p></pre><pre>across their entire third-party exposed development interface, but one<o:p></o:p></pre><pre>also has to question the path vbox seems to have gone down as well. My<o:p></o:p></pre><pre>own suggestion is to abandon the VS/SDK toolchain entirely and stick<o:p></o:p></pre><pre>with the WDK toolchain for the entire windows build environment, as that<o:p></o:p></pre><pre>set of libraries and include files works from user mode down through<o:p></o:p></pre><pre>kernel mode, at the cost of not always current user mode windows UI<o:p></o:p></pre><pre>related support.<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>-----Original Message-----<o:p></o:p></pre><pre>From: <a href="mailto:vbox-dev-bounces@virtualbox.org">vbox-dev-bounces@virtualbox.org</a><o:p></o:p></pre><pre>[<a href="mailto:vbox-dev-bounces@virtualbox.org">mailto:vbox-dev-bounces@virtualbox.org</a>] On Behalf Of Perry Halbert<o:p></o:p></pre><pre>Sent: Monday, August 01, 2011 11:24 AM<o:p></o:p></pre><pre>To: <a href="mailto:vbox-dev@virtualbox.org">vbox-dev@virtualbox.org</a><o:p></o:p></pre><pre>Subject: [vbox-dev] Windows OSE compile<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>Trying to compile the Windows OSE version seems to fail no matter which<o:p></o:p></pre><pre>version I try. At least back to 2.2.4 which should still have been in<o:p></o:p></pre><pre>the time frame of the posted instructions. I have read references that<o:p></o:p></pre><pre>I should edit intrin.h on Visual Studio 2005, but I find that hard to<o:p></o:p></pre><pre>believe. Is this true? and if so do you have a working copy of this<o:p></o:p></pre><pre>file or patch?<o:p></o:p></pre><pre><o:p> </o:p></pre><pre><o:p> </o:p></pre><pre><o:p> </o:p></pre><pre><o:p> </o:p></pre><pre>Microsoft (R) Windows Script Host Version 5.7 Copyright (C) Microsoft<o:p></o:p></pre><pre>Corporation. All rights reserved.<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>Shell inheritance test: OK<o:p></o:p></pre><pre>Source path: OK<o:p></o:p></pre><pre>Checking for kBuild...<o:p></o:p></pre><pre> Found kBuild: E:/trunk/kBuild<o:p></o:p></pre><pre> Found kBuild binaries: E:/trunk/kBuild/bin/win.x86 Checking for<o:p></o:p></pre><pre>Windows 2003 DDK, build 3790 or later...<o:p></o:p></pre><pre> Found Windows 2003 DDK: E:/WINDDK/3790.1830 Checking for Visual C++...<o:p></o:p></pre><pre> Found Visual C++ v8 (or later): C:/PROGRA~1/MICROS~2/VC (C:/Program<o:p></o:p></pre><pre>Files/Microsoft Visual Studio 8/VC) Checking for Windows Platform SDK<o:p></o:p></pre><pre>(recent)...<o:p></o:p></pre><pre> Found Windows Platform SDK: C:/PROGRA~1/MI2578~1/Windows/v6.1<o:p></o:p></pre><pre>(C:/Program Files/Microsoft SDKs/Windows/v6.1) Checking for Midl.exe...<o:p></o:p></pre><pre> Found Midl.exe: C:/PROGRA~1/MI2578~1/Windows/v6.1/bin/Midl.exe<o:p></o:p></pre><pre>(C:/Program Files/Microsoft SDKs/Windows/v6.1/Bin/Midl.exe) Checking for<o:p></o:p></pre><pre>Direct X SDK...<o:p></o:p></pre><pre> Found Direct X SDK: C:/PROGRA~1/MI22C6~1 (C:/Program Files/Microsoft<o:p></o:p></pre><pre>DirectX SDK (October 2006)) Checking for MinGW GCC v3.3.x + Binutils +<o:p></o:p></pre><pre>Runtime + W32API...<o:p></o:p></pre><pre> Found MinGW (GCC v3.3.3): E:/MinGW<o:p></o:p></pre><pre> Found W32API: E:\MinGW<o:p></o:p></pre><pre>Checking for libSDL...<o:p></o:p></pre><pre> Found libSDL: E:/SDL-1.2.14-win32<o:p></o:p></pre><pre>Checking for libxml2...<o:p></o:p></pre><pre> Found libxml2: E:/libxml2-2.7.8.win32<o:p></o:p></pre><pre>Checking for libxslt...<o:p></o:p></pre><pre> Found libxslt: E:/libxslt-1.0.32.win32 Checking for openssl...<o:p></o:p></pre><pre> Found openssl: E:/OpenSSL-Win32<o:p></o:p></pre><pre>Checking for libcurl...<o:p></o:p></pre><pre> Found libcurl: E:/libcurl<o:p></o:p></pre><pre>Checking for Qt4...<o:p></o:p></pre><pre> Found Qt4 : E:/QT4<o:p></o:p></pre><pre>Checking for Python...<o:p></o:p></pre><pre> Found Python : E:\Python27<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>(I also have Gsoap-2.7 installed which works fine and reference in<o:p></o:p></pre><pre>LocalConfig.kmk)<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>Execute env.bat once before you start to build VBox:<o:p></o:p></pre><pre><o:p> </o:p></pre><pre> env.bat<o:p></o:p></pre><pre> kmk<o:p></o:p></pre><pre><o:p> </o:p></pre><pre><o:p> </o:p></pre><pre>C:\PROGRA~1\MICROS~2\VC\include\intrin.h(944) : error C2733: second C<o:p></o:p></pre><pre>linkage of overloaded function '_interlockedbittestandset' not allowed<o:p></o:p></pre><pre> C:\PROGRA~1\MICROS~2\VC\include\intrin.h(944) : see declaration<o:p></o:p></pre><pre>of '_interlockedbittestandset'<o:p></o:p></pre><pre>C:\PROGRA~1\MICROS~2\VC\include\intrin.h(945) : error C2733: second C<o:p></o:p></pre><pre>linkage of overloaded function '_interlockedbittestandreset' not allowed<o:p></o:p></pre><pre> C:\PROGRA~1\MICROS~2\VC\include\intrin.h(945) : see declaration<o:p></o:p></pre><pre>of '_interlockedbittestandreset'<o:p></o:p></pre><pre>kmk: ***<o:p></o:p></pre><pre>[E:/trunk/out/win.x86/release/obj/RuntimeBldProg/r3/alloc-ef.obj] Error<o:p></o:p></pre><pre>2<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>_______________________________________________<o:p></o:p></pre><pre>vbox-dev mailing list<o:p></o:p></pre><pre><a href="mailto:vbox-dev@virtualbox.org">vbox-dev@virtualbox.org</a><o:p></o:p></pre><pre><a href="http://vbox.innotek.de/mailman/listinfo/vbox-dev">http://vbox.innotek.de/mailman/listinfo/vbox-dev</a><o:p></o:p></pre><pre><o:p> </o:p></pre></div></body></html>