search for: vcbuild

Hi, Yesterday I upgraded to kernel 2.6.8 on my Fedora Core 2 system. This caused a problem with the version of wine I'd been using (20040505), so I upgraded wine to the current version (20040813). The remaining problem is as follows: I'm calling wine like this: wine start.exe vcbuild.bat and vcbuild.bat contains the following: set QMAKESPEC=win32-msvc.net set QTDIR=F:\wine\qt\3.2.1-nc\msvc.net set PATH=%PATH%;%QTDIR%\bin set PATH=F:\wine\msvc++tk2003\bin;%PATH% set INCLUDE=F:\wine\msvc++tk2003\include;F:\wine\OpenSSL\include;%INCLUDE% set LIB=F:\wine\msvc++...

...mmand-line (but I'm guessing it's not, since MSBuild is used internally > inside VS), or if the file-copy is being prevented by something in my > environment (files are marked writable, I already checked). The MSBuild infrastructure isn't used by VS 2005 for C++ projects; rather, VCBuild does the work. I'm not sure about VS 2008. FWIW, I used ProcMon to diagnose file-handling issues I had in my build: http://technet.microsoft.com/en-us/sysinternals/bb896645.aspx -- Barry -- http://barrkel.blogspot.com/

...mpared to the 16k or so for the config.h file in $LLVM-ROOT/include/llvm/Config. The contents are obviously different, as well, since the one in $LLVM-ROOT/include/llvm/Config has the LLVM_ON_UNIX #define set. It didn't appear to be doing the copy even when building from within VS. Using "vcbuild /clean" then "vcbuild" on the Configure.vcproj file directly seems to have forced the copy to take place. I can see the "1 file(s) copied" output in the BuildLog. Except it doesn’t. File date/time reveals that nothing's been done to it, and opening it up confirms that...

...Project "C:\Prg\llvm-2.2\llvm-2.2\win32\llvm.sln" (Build target(s)): Target ValidateSolutionConfiguration: Building solution configuration "Debug|Win32". Target Build: Target Configure: C:\Program Files\Microsoft Visual Studio 8\Common7\IDE\..\..\vc\vcpackag es\vcbuild.exe C:\Prg\llvm-2.2\llvm-2.2\win32\Configure\Configure.vcproj "Config ure|Win32" Target support: C:\Program Files\Microsoft Visual Studio 8\Common7\IDE\..\..\vc\vcpackag es\vcbuild.exe C:\Prg\llvm-2.2\llvm-2.2\win32\Support\Support.tmp_Debug_Win32.vc proj "Debug|Win32&quo...

...Project "C:\Prg\llvm-2.2\llvm-2.2\win32\llvm.sln" (Build target(s)): Target ValidateSolutionConfiguration: Building solution configuration "Debug|Win32". Target Build: Target Configure: C:\Program Files\Microsoft Visual Studio 8\Common7\IDE\..\..\vc\vcpackag es\vcbuild.exe C:\Prg\llvm-2.2\llvm-2.2\win32\Configure\Configure.vcproj "Config ure|Win32" Target support: C:\Program Files\Microsoft Visual Studio 8\Common7\IDE\..\..\vc\vcpackag es\vcbuild.exe C:\Prg\llvm-2.2\llvm-2.2\win32\Support\Support.tmp_Debug_Win32.vc proj "Debug|Win32&quo...

By the way, somebody (I think it was Chuck, but I don't remember for certain) was asking for the BuildLog.htm from building the llvm.sln file under VS 2005 SP1 for diagnostic purposes; right now the SLN is configured to produce a new BuildLog for each and every one of the projects inside the solution. I don't know who's responsible for this guy, but that's probably not the best way

So far, Firefox (with msvc 2005) and a couple other apps (one using open watcom) build properly on wine. I'm pecking away at the problems that get in the way (particularly cmd bugs at the moment). If you're trying to build a Windows app on Wine by running your normal Windows build procedure (as opposed to using winegcc), I'd like to hear from you, especially if a bug in cmd or some

...he Microsoft environment for writing drivers. Actually Windows itself (all of it) is compiled with this tool. Basically the compiler and tools come from the same code base as the Microsoft Visual Studio compilers, but without all GUI junk and with a *sane* build system instead of the horrid msbuild/vcbuild. It works very well, I am very happy with this. I have chosen the WDK instead of GNU tools because I already use it for writing windows drivers and it works really really well. I want to change it though because: 1) It knows only IA-32(e) and IA-64. Right now I only target IA-32e (x64) but I'...