I'm trying to get the wine tests to compile under msvc, so I ran msvcmaker in the wine source under cygwin (which was successful). Then I opened the winetest project and did a 'rebuild all'. When it tries to compile advapi32_test/security.c I get an warning and 102 errors: C:\Program Files\Microsoft Visual Studio\VC98\INCLUDE\rpc.h(89) : warning C4005: 'RPCRTAPI' : macro redefinition ..\..\..\include\rpc.h(45) : see previous definition of 'RPCRTAPI' :\Program Files\Microsoft Visual Studio\VC98\INCLUDE\rpcnsi.h(37) : error C2143: syntax error : missing ')' before 'type' C:\Program Files\Microsoft Visual Studio\VC98\INCLUDE\rpcnsi.h(37) : error C2491: 'RpcNsBindingExportA' : definition of dllimport function not allowed ......etc I'm pretty sure the problem is that the the msvc's rpc.h and rpcnsi.h files are being included when they shouldn't. Is that about right? If so, what could be a possible solution? BTW I'm compiling with MSVC++ 6.0. wine cvs from 11-01-2004. -- James Hawkins
On Mon, 1 Nov 2004, James Hawkins wrote: [...]
I'm pretty sure the problem is that the the msvc's rpc.h and rpcnsi.h files are being included when they shouldn't. Is that about right? If so, what could be a possible solution?
BTW I'm compiling with MSVC++ 6.0. wine cvs from 11-01-2004.
Two questions: * Have you checked the following section of the Wine Developer's Guide? Building and running the tests on Windows http://www.winehq.org/site/docs/wine-devel/testing-windows * You say that you use MSVC 6.0. Did you also install a recent Platform SDK? If not the tests won't compile as stated in the above documentation. As of a few days ago, I was able to compile all of the Wine conformance tests (not the Wine dlls themselves) using: the MSVC targets, MSVC 6.0, a recent Platform SDK and a recent Direct X SDK. -- Francois Gouget fgouget(a)free.fr http://fgouget.free.fr/ In a world without fences who needs Gates?
* You say that you use MSVC 6.0. Did you also install a recent Platform SDK? If not the tests won't compile as stated in the above documentation.
I have not done that yet. I will install the platform sdk and then see if it works. On Tue, 2 Nov 2004 01:10:41 +0100 (CET), Francois Gouget <fgouget(a)free.fr> wrote:
On Mon, 1 Nov 2004, James Hawkins wrote: [...]
I'm pretty sure the problem is that the the msvc's rpc.h and rpcnsi.h files are being included when they shouldn't. Is that about right? If so, what could be a possible solution?
BTW I'm compiling with MSVC++ 6.0. wine cvs from 11-01-2004.
Two questions:
* Have you checked the following section of the Wine Developer's Guide?
Building and running the tests on Windows http://www.winehq.org/site/docs/wine-devel/testing-windows
* You say that you use MSVC 6.0. Did you also install a recent Platform SDK? If not the tests won't compile as stated in the above documentation.
As of a few days ago, I was able to compile all of the Wine conformance tests (not the Wine dlls themselves) using: the MSVC targets, MSVC 6.0, a recent Platform SDK and a recent Direct X SDK.
-- Francois Gouget fgouget(a)free.fr http://fgouget.free.fr/ In a world without fences who needs Gates?
-- James Hawkins
On Tue, Nov 02, 2004 at 01:10:41AM +0100, Francois Gouget wrote:
As of a few days ago, I was able to compile all of the Wine conformance tests (not the Wine dlls themselves) using: the MSVC targets, MSVC 6.0, a recent Platform SDK and a recent Direct X SDK.
It would be really cool if we: 1. Had documentation on how to do the above (building the tests with MSVC) from within Linux via Wine. 2. Could actually build the dlls themselves with MSVC. Any efforts in that direction? Did anyone try this? If so, we could track the progress on the Fun Projects page. -- Dimi
I have installed the latest platform SDk and directx SDK, and set up msvc per http://www.winehq.org/site/docs/wine-devel/testing-windows, but I get this error when compiling dsound_test: Linking... uuid.lib(unknwn_i.obj) : fatal error LNK1103: debugging information corrupt; recompile module Error executing link.exe. wineruntests.exe - 1 error(s), 11 warning(s) Any ideas? On Mon, 1 Nov 2004 22:39:39 -0500, Dimitrie O. Paun <dpaun(a)rogers.com> wrote:
On Tue, Nov 02, 2004 at 01:10:41AM +0100, Francois Gouget wrote:
As of a few days ago, I was able to compile all of the Wine conformance tests (not the Wine dlls themselves) using: the MSVC targets, MSVC 6.0, a recent Platform SDK and a recent Direct X SDK.
It would be really cool if we: 1. Had documentation on how to do the above (building the tests with MSVC) from within Linux via Wine. 2. Could actually build the dlls themselves with MSVC. Any efforts in that direction? Did anyone try this? If so, we could track the progress on the Fun Projects page.
-- Dimi
-- James Hawkins
On Tue, 2 Nov 2004, James Hawkins wrote:
I have installed the latest platform SDk and directx SDK, and set up msvc per http://www.winehq.org/site/docs/wine-devel/testing-windows, but I get this error when compiling dsound_test:
Linking... uuid.lib(unknwn_i.obj) : fatal error LNK1103: debugging information corrupt; recompile module Error executing link.exe.
wineruntests.exe - 1 error(s), 11 warning(s)
Any ideas?
My theory (haven't had time to test yet), is that the latest Platform SDK is incompatible with MSVC 6. Using th enew headers but linking with the libraries from a slightly older Platform SDK solve this error. -- Francois Gouget fgouget(a)free.fr http://fgouget.free.fr/ I haven't lost my mind, it's backed up on tape around here somewhere...
Using the new headers but linking with the libraries from a slightly older Platform SDK solve this error.
Which slightly older Platform SDK do you use? On Wed, 3 Nov 2004 12:25:01 +0100 (CET), Francois Gouget <fgouget(a)free.fr> wrote:
On Tue, 2 Nov 2004, James Hawkins wrote:
I have installed the latest platform SDk and directx SDK, and set up msvc per http://www.winehq.org/site/docs/wine-devel/testing-windows, but I get this error when compiling dsound_test:
Linking... uuid.lib(unknwn_i.obj) : fatal error LNK1103: debugging information corrupt; recompile module Error executing link.exe.
wineruntests.exe - 1 error(s), 11 warning(s)
Any ideas?
My theory (haven't had time to test yet), is that the latest Platform SDK is incompatible with MSVC 6. Using th enew headers but linking with the libraries from a slightly older Platform SDK solve this error.
-- Francois Gouget fgouget(a)free.fr http://fgouget.free.fr/ I haven't lost my mind, it's backed up on tape around here somewhere...
-- James Hawkins
participants (3)
-
Dimitrie O. Paun -
Francois Gouget -
James Hawkins