> 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
<[EMAIL PROTECTED]> wrote:
> On Tue, 2 Nov 2004, James Hawkins wrote:
>
>
>
> > I
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 info
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
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:
> * 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
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 questio
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\Micro
On Tue, 05 Oct 2004 11:10:45 +0100, Martin Fuchs <[EMAIL PROTECTED]> wrote:
> OK, here is the next problem.
> The tool msvcmaker prints the following error messages:
>
> $ tools/winapi/msvcmaker
> Global symbol "$wine_dir" requires explicit package name at tools/winapi/msvcmaker
> line 52.
I took
Hello Francois,
> It looks like it does not find the $wine_dir declaration. We are
> supposed to import it from the config module which in fact imports it
> from the setup module. Does it work better if you edit
> tools/winapi/msvcmaker as follows?
It seems, that's not enough. Then it can't fi
On Tue, 5 Oct 2004, Martin Fuchs wrote:
OK, here is the next problem.
The tool msvcmaker prints the following error messages:
$ tools/winapi/msvcmaker
Global symbol "$wine_dir" requires explicit package name at tools/winapi/msvcmaker
line 52.
[...]
Execution of tools/winapi/msvcmaker aborted due t
OK, here is the next problem.
The tool msvcmaker prints the following error messages:
$ tools/winapi/msvcmaker
Global symbol "$wine_dir" requires explicit package name at tools/winapi/msvcmaker
line 52.
Global symbol "$wine_dir" requires explicit package name at tools/winapi/msvcmaker
line 116.
11 matches
Mail list logo