Re: Temporary fix to trying to put a pointer in a DWORD

Vincent Béron wrote: Le sam 16/10/2004 à 23:54, Dmitry Timoshkov a écrit : "Vincent Béron" <[EMAIL PROTECTED]> wrote: We try to put a pointer in a DWORD in a static initialization of CRITICAL_SECTION_DEBUGs. Of course it doesn't work on Win64. We'll have to find a better solution though.

Re: winesetuptk0.72/tcltk-winesetuptk-0.72

> /tcltk-winesetuptk-0.72/build.sh Winesetuptk isn't maintained any more, and it isn't needed to configure wine. Why do you need it? Ivan. Libero ADSL: navighi gratis a 1.2 Mega, senza canone e costi di attivazione. Abbonati subito s

Re: Honor --disable-debug or --disable-trace completely

Le sam 16/10/2004 à 22:29, Vincent Béron a écrit : > (Yes, the patch is gzip as it's over 200k) > > wine/debug.h has some tests based on NO_{DEBUG,TRACE}_MSGS, which is set > (or not) in config.h. Quite a few files didn't #include config.h before > wine/debug.h, so some debugmsgs were always compi

Re: Temporary fix to trying to put a pointer in a DWORD

Le sam 16/10/2004 à 23:54, Dmitry Timoshkov a écrit : > "Vincent Béron" <[EMAIL PROTECTED]> wrote: > > > We try to put a pointer in a DWORD in a static initialization of > > CRITICAL_SECTION_DEBUGs. Of course it doesn't work on Win64. We'll have > > to find a better solution though. > > Another w

Re: Use LLP64 compatible sized-types for LONG and DWORD

"Vincent Béron" <[EMAIL PROTECTED]> wrote: > > It would be cleaner IMO to use that only when compiling with _WIN64 defined, > > that would avoid affecting the Win32 target. > > Dimi thought like you (and me too), but that's not what Alexandre > thought on IRC yesterday. One of the things is that i

Re: Temporary fix to trying to put a pointer in a DWORD

"Vincent Béron" <[EMAIL PROTECTED]> wrote: > We try to put a pointer in a DWORD in a static initialization of > CRITICAL_SECTION_DEBUGs. Of course it doesn't work on Win64. We'll have > to find a better solution though. Another way to fix it is to use full 'DWORD Spare[2]' to store a pointer on W

Re: Use LLP64 compatible sized-types for LONG and DWORD

Le sam 16/10/2004 à 23:45, Dmitry Timoshkov a écrit : > "Vincent Béron" <[EMAIL PROTECTED]> wrote: > > > Changelog: > > Change the type of LONG and DWORD to be int based instead of long based > > for Win64 compatibility. > > It would be cleaner IMO to use that only when compiling with _WIN64 defi

Re: Use LLP64 compatible sized-types for LONG and DWORD

"Vincent Béron" <[EMAIL PROTECTED]> wrote: > Changelog: > Change the type of LONG and DWORD to be int based instead of long based > for Win64 compatibility. It would be cleaner IMO to use that only when compiling with _WIN64 defined, that would avoid affecting the Win32 target. -- Dmitry.

Re: Fix various function prototypes

Le sam 16/10/2004 à 23:39, Dmitry Timoshkov a écrit : > "Vincent Béron" <[EMAIL PROTECTED]> wrote: > > > > According to Platform SDK headers SHCoCreateInstance returns HRESULT. > > > > MSDN says it's void > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/shellcc/platform/shell/r

Re: Fix various function prototypes

"Vincent Béron" <[EMAIL PROTECTED]> wrote: > > According to Platform SDK headers SHCoCreateInstance returns HRESULT. > > MSDN says it's void > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/shellcc/platform/shell/reference/functions/shcocreateinstance.asp Hmm, MSDN Library Janua

Re: Fix various function prototypes

Le sam 16/10/2004 à 23:17, Dmitry Timoshkov a écrit : > "Vincent Béron" <[EMAIL PROTECTED]> wrote: > > > SHCoCreateInstance returns void, not HRESULT. > > According to Platform SDK headers SHCoCreateInstance returns HRESULT. MSDN says it's void http://msdn.microsoft.com/library/default.asp?url=/

Re: Fix various function prototypes

"Vincent Béron" <[EMAIL PROTECTED]> wrote: > SHCoCreateInstance returns void, not HRESULT. According to Platform SDK headers SHCoCreateInstance returns HRESULT. P.S. Do you compile Wine with _WIN64 defined on Alpha? That would be really cool to see that going, clean our headers and fix all warni

Re: RFH: winuser.h

On Thu, 14 Oct 2004, Dimitrie O. Paun wrote: Can someone please help me with the value of LBS_COMBOBOX? According to the Platform SDK its value is 0x8000L. -- Francois Gouget [EMAIL PROTECTED]http://fgouget.free.fr/ 1 + e ^ ( i * pi ) = 0

Re: programs/winecfg/libraries.c warnings regressions

Le sam 16/10/2004 à 09:11, Gerald Pfeifer a écrit : [snip] > >libraries.c:261: warning: `mode' might be used uninitialized in this function >libraries.c:264: warning: `str' might be used uninitialized in this function > > (which are the only ones of this kind for a full Wine build). Depe

Re: programs/winecfg/winecfg.c and setkey()

Le sam 16/10/2004 à 09:19, Gerald Pfeifer a écrit : > programs/winecfg/winecfg.c now defines a function called setkey(). > > This same function also appears in stdlib.h and unistd.h on FreeBSD 5.x > systems, so the build on these platforms fails with > >winecfg.c:136: error: conflicting types

programs/winecfg/libraries.c warnings regressions

I believe the following patch of programs/winecfg/libraries.c revision 1.3 date: 2004/09/28 03:55:16; author: julliard; state: Exp; lines: +288 -501 Mike Hearn <[EMAIL PROTECTED]> - rewrite the transaction system to be based on a settings overlay, to have a nicer API, and to actually

programs/winecfg/winecfg.c and setkey()

programs/winecfg/winecfg.c now defines a function called setkey(). This same function also appears in stdlib.h and unistd.h on FreeBSD 5.x systems, so the build on these platforms fails with winecfg.c:136: error: conflicting types for `setkey' /usr/include/stdlib.h:211: error: previous declarat