wine-devel

wine-devel@winehq.org

84463 discussions

Compilation error with newer CVS on glibc -2.0
by Martin Cracauer 02 Aug '02

02 Aug '02

Hi, guys, since Jul 20 or so I get this compilation error on glibc-2.1.3/linux-2.4.18: gcc -c -I. -I. -I../../include -I../../include -g -O2 -Wall -fno-strength-reduce -mpreferred-stack-boundary=2 -D__WINE__ -D_REENTRANT -I/usr/X11R6/include -o wrc.o wrc.c In file included from wrc.h:25, from wrc.c:61: wrctypes.h:447: redefinition of `struct user' make[2]: *** [wrc.o] Error 1 make[2]: Leaving directory `/disks/part9/home/cracauer/work/cvs-packages-work/stupids/wine/wine/tools/wrc' Wine's definition of struct user is clashing with the one from /usr/include/sys/user.h Now, it appears that /usr/include/sys/user.h (a glibc-2.1.3 file) is in error having this struct in first place, since newer kernels have this struct in asm/user.h. I fixed the problem in my /usr/include, but I guess it is better to use a different name for the struct in Wine to be compatible with this configuration (it's Debian-2.1 with an upgraded kernel). Unless somebody disagrees with that analysis, I'll submit a patch to rename the struct. Suggestions about a suitable name welcome. Martin

2 4

Translation wine documentation to other languages
by Andriy Palamarchuk 01 Aug '02

01 Aug '02

Sorry for crossposting initial message to both lists. I think the topic may be interesting for both - users and developers. Any volunteers to help to translate the documentation to languages other than English? This is very big job, so there can be more than one person, working on the same language. Among responses to my call for volunteers I got response from Pedro Restrepo suggesting his help in Wine localization. See his message below. Damian Wojslaw requested information on the same topic on wine-users. --- Pedro Restrepo <pedrores(a)tutopia.com> wrote: > Hi Andiry, > > First, thank you and thanks to all people working on > Wine. I am using > Wine to run Lotus Notes Client on Linux. At the > moment, we are testing > it. > > I want to help on Wine project. I propose you one > new work: Wine > translation to spanish (documentation, installer, > web site info, etc). I > think in this work because I think this project is > necessary for all > people who need transition tools from Windows to > Linux and there are > many people in this situation in SouthAmerica (I am > from Colombia and I > am tired of the big payments for software in our > poor nations). Currently Wine does not have official documentation in other languages. Some winelib applications are localized to other languages. Documents with highest priority for translation: * README file * Wine User Guide * user-oriented pages on Winehq Plus, we'll need to keep translations in sync with original documentation. Comments, ideas, suggestions? Andriy __________________________________________________ Do You Yahoo!? Yahoo! - Official partner of 2002 FIFA World Cup http://fifaworldcup.yahoo.com

2 1

Re: PATCH: Convert HMIDI to void*
by Eric Pouech 01 Aug '02

01 Aug '02

Michael Stefaniuc a écrit : > > Hello, > > am I right that HMIDI and HMIDIIN, HMIDIOUT shouldn't be > interchangeable? Would save some conversions. > > License: LGPL, X11 > Changelog: > Michael Stefaniuc <mstefani(a)redhat.com> > Convert HMIDI to a void* I just modified a bit Michael's patch: - better fix for midimap file - changed all HMIDI???? Alexandre, use this version instead. A+ Name: mm_midih ChangeLog: HMIDI??? handles are no long OLD_HANDLE License: X11 GenDate: 2002/08/01 07:11:07 UTC ModifiedFiles: dlls/winmm/lolvldrv.c dlls/winmm/mmsystem.c dlls/winmm/mciseq/mcimidi.c dlls/winmm/midimap/midimap.c include/mmsystem.h AddedFiles: =================================================================== RCS file: /home/cvs/cvsroot/wine/wine/dlls/winmm/lolvldrv.c,v retrieving revision 1.29 diff -u -u -r1.29 lolvldrv.c --- dlls/winmm/lolvldrv.c 3 Jul 2002 21:10:44 -0000 1.29 +++ dlls/winmm/lolvldrv.c 1 Aug 2002 06:51:25 -0000 @@ -693,7 +693,7 @@ *(LPDWORD)((char*)ptr + sizeof(LPMIDIOPENDESC)) = *lpdwUser; mod16 = (LPMIDIOPENDESC16)((LPSTR)ptr + sizeof(LPMIDIOPENDESC) + 2*sizeof(DWORD)); - mod16->hMidi = mod32->hMidi; + mod16->hMidi = LOWORD(mod32->hMidi); mod16->dwCallback = mod32->dwCallback; mod16->dwInstance = mod32->dwInstance; mod16->dnDevNode = mod32->dnDevNode; Index: dlls/winmm/mmsystem.c =================================================================== RCS file: /home/cvs/cvsroot/wine/wine/dlls/winmm/mmsystem.c,v retrieving revision 1.63 diff -u -u -r1.63 mmsystem.c --- dlls/winmm/mmsystem.c 29 Jul 2002 23:29:23 -0000 1.63 +++ dlls/winmm/mmsystem.c 1 Aug 2002 06:51:25 -0000 @@ -2188,7 +2188,7 @@ *lphMidiOut = hMidiOut; if (lpwm) { - lpwm->mod.hMidi = hMidiOut; + lpwm->mod.hMidi = (HMIDI) hMidiOut; lpwm->mod.dwCallback = *lpdwCallback; lpwm->mod.dwInstance = *lpdwInstance; lpwm->mod.dnDevNode = 0; @@ -2739,7 +2739,7 @@ if (lpwm == NULL) return MMSYSERR_NOMEM; - lpwm->mod.hMidi = hMidiIn; + lpwm->mod.hMidi = (HMIDI) hMidiIn; lpwm->mod.dwCallback = dwCallback; lpwm->mod.dwInstance = dwInstance; Index: dlls/winmm/mciseq/mcimidi.c =================================================================== RCS file: /home/cvs/cvsroot/wine/wine/dlls/winmm/mciseq/mcimidi.c,v retrieving revision 1.16 diff -u -u -r1.16 mcimidi.c --- dlls/winmm/mciseq/mcimidi.c 31 May 2002 23:40:57 -0000 1.16 +++ dlls/winmm/mciseq/mcimidi.c 1 Aug 2002 06:51:25 -0000 @@ -817,7 +817,7 @@ wmm->dwStatus = MCI_MODE_NOT_READY; if (oldstat == MCI_MODE_PAUSE) - dwRet = midiOutReset(wmm->hMidi); + dwRet = midiOutReset((HMIDIOUT)wmm->hMidi); while (wmm->dwStatus != MCI_MODE_STOP) Sleep(10); @@ -962,7 +962,7 @@ MIDI_mciReadNextEvent(wmm, mmt); /* FIXME == 0 */ } - dwRet = midiOutOpen(&wmm->hMidi, MIDIMAPPER, 0L, 0L, CALLBACK_NULL); + dwRet = midiOutOpen((LPHMIDIOUT)&wmm->hMidi, MIDIMAPPER, 0L, 0L, CALLBACK_NULL); /* dwRet = midiInOpen(&wmm->hMidi, MIDIMAPPER, 0L, 0L, CALLBACK_NULL);*/ if (dwRet != MMSYSERR_NOERROR) { return dwRet; @@ -1142,7 +1142,7 @@ break; default: if (doPlay) { - dwRet = midiOutShortMsg(wmm->hMidi, mmt->dwEventData); + dwRet = midiOutShortMsg((HMIDIOUT)wmm->hMidi, mmt->dwEventData); } else { switch (LOBYTE(LOWORD(mmt->dwEventData)) & 0xF0) { case MIDI_NOTEON: @@ -1150,7 +1150,7 @@ dwRet = 0; break; default: - dwRet = midiOutShortMsg(wmm->hMidi, mmt->dwEventData); + dwRet = midiOutShortMsg((HMIDIOUT)wmm->hMidi, mmt->dwEventData); } } } @@ -1163,9 +1163,9 @@ } } - midiOutReset(wmm->hMidi); + midiOutReset((HMIDIOUT)wmm->hMidi); - dwRet = midiOutClose(wmm->hMidi); + dwRet = midiOutClose((HMIDIOUT)wmm->hMidi); /* to restart playing at beginning when it's over */ wmm->dwPositionMS = 0; @@ -1212,7 +1212,7 @@ midiHdr.dwBufferLength = 1024; midiHdr.dwUser = 0L; midiHdr.dwFlags = 0L; - dwRet = midiInPrepareHeader(wmm->hMidi, &midiHdr, sizeof(MIDIHDR)); + dwRet = midiInPrepareHeader((HMIDIIN)wmm->hMidi, &midiHdr, sizeof(MIDIHDR)); TRACE("After MIDM_PREPARE \n"); wmm->dwStatus = MCI_MODE_RECORD; /* FIXME: there is no buffer added */ @@ -1220,12 +1220,12 @@ TRACE("wmm->dwStatus=%p %d\n", &wmm->dwStatus, wmm->dwStatus); midiHdr.dwBytesRecorded = 0; - dwRet = midiInStart(wmm->hMidi); + dwRet = midiInStart((HMIDIIN)wmm->hMidi); TRACE("midiInStart => dwBytesRecorded=%lu\n", midiHdr.dwBytesRecorded); if (midiHdr.dwBytesRecorded == 0) break; } TRACE("Before MIDM_UNPREPARE \n"); - dwRet = midiInUnprepareHeader(wmm->hMidi, &midiHdr, sizeof(MIDIHDR)); + dwRet = midiInUnprepareHeader((HMIDIIN)wmm->hMidi, &midiHdr, sizeof(MIDIHDR)); TRACE("After MIDM_UNPREPARE \n"); if (midiHdr.lpData != NULL) { HeapFree(GetProcessHeap(), 0, midiHdr.lpData); @@ -1255,7 +1255,7 @@ /* stop all notes */ unsigned chn; for (chn = 0; chn < 16; chn++) - midiOutShortMsg(wmm->hMidi, 0x78B0 | chn); + midiOutShortMsg((HMIDIOUT)(wmm->hMidi), 0x78B0 | chn); wmm->dwStatus = MCI_MODE_PAUSE; } if (lpParms && (dwFlags & MCI_NOTIFY)) { Index: dlls/winmm/midimap/midimap.c =================================================================== RCS file: /home/cvs/cvsroot/wine/wine/dlls/winmm/midimap/midimap.c,v retrieving revision 1.13 diff -u -u -r1.13 midimap.c --- dlls/winmm/midimap/midimap.c 31 May 2002 23:40:57 -0000 1.13 +++ dlls/winmm/midimap/midimap.c 1 Aug 2002 06:46:12 -0000 @@ -81,7 +81,7 @@ { char name[MAXPNAMELEN]; int loaded; - HMIDI hMidi; + HMIDIOUT hMidi; unsigned short uDevID; LPBYTE lpbPatch; unsigned int aChn[16]; Index: include/mmsystem.h =================================================================== RCS file: /home/cvs/cvsroot/wine/wine/include/mmsystem.h,v retrieving revision 1.51 diff -u -u -r1.51 mmsystem.h --- include/mmsystem.h 31 May 2002 23:06:48 -0000 1.51 +++ include/mmsystem.h 1 Aug 2002 06:52:49 -0000 @@ -34,10 +34,10 @@ DECLARE_OLD_HANDLE(HWAVE); DECLARE_OLD_HANDLE(HWAVEIN); DECLARE_OLD_HANDLE(HWAVEOUT); -DECLARE_OLD_HANDLE(HMIDI); -DECLARE_OLD_HANDLE(HMIDIIN); -DECLARE_OLD_HANDLE(HMIDIOUT); -DECLARE_OLD_HANDLE(HMIDISTRM); +DECLARE_HANDLE(HMIDI); +DECLARE_HANDLE(HMIDIIN); +DECLARE_HANDLE(HMIDIOUT); +DECLARE_HANDLE(HMIDISTRM); DECLARE_OLD_HANDLE(HMIXER); DECLARE_OLD_HANDLE(HMIXEROBJ); DECLARE_OLD_HANDLE(HMMIO);

3 2

Netbios and Wins support
by Claudiu Costin 01 Aug '02

01 Aug '02

Dear friends, Is there anybody working on Netbios/MS Windows Network support? I want to run Outlook with Exchange. I can help testing and hacking, but not writing real code. kind regards, -- Claudiu Costin, claudiuc(a)kde.org Linux-KDE Romania http://www.ro.kde.org

2 1

Re: PATCH: Convert HMIDI to void*
by Eric Pouech 31 Jul '02

31 Jul '02

Michael Stefaniuc a écrit : > > Hello, > > am I right that HMIDI and HMIDIIN, HMIDIOUT shouldn't be > interchangeable? Would save some conversions. yes & no HMIDIIN cannot be used for a HMIDIOUT (anyway, this will be checked internally by our mmsys implementation: all HMIDI???? handles are stored in the same table, and we never rely on the HMIDI??? handle type but on the actual object type) however, HMIDI can be used for a HMIDIIN (or HMIDIOUT or HMIDISTRM) handle (see midiConnect for example) it's true that midimap dll should use HMIDIOUT instead of HMIDI in its internal data structure A+

3 4

Toolbar redraw problem
by dusanv 31 Jul '02

31 Jul '02

Hi, I am seeing a bunch of apps have redrawing problems when a toolbar is dragged accross the window. Here's a screen shot: http://dusanv.net/files/wine-ss.png Does anyone have any info on this? I'd like to fix it but can't find anyhting relevant. TIA, Dusan

2 2

Re: PATCH: a bit further with a cygwin build (fixed patch)
by Francois Gouget 31 Jul '02

31 Jul '02

On Tue, 30 Jul 2002, Rafael Kitover wrote: > Sorry, due to brain-deadness on my part the previous version of this > patch didn't build properly. This version is much cleaner and builds > properly on linux. > +#ifndef HAVE__FSTAT > int _fstat(int fd, struct _stat* buf) > +#else > +int MSVCRT(_fstat)(int fd, struct _stat* buf) > +#endif /* HAVE__FSTAT */ ... > +#ifndef HAVE__STAT > int _stat(const char* path, struct _stat * buf) > +#else > +int MSVCRT(_stat)(const char* path, struct _stat * buf) > +#endif /* HAVE__STAT */ You should systematically use MSVCRT(_fstat) and MSVCRT(_stat). Your previous patch was better :-) Basically, we use MSVCRT(xxx) for all symbols for which we may get a conflict with the native C library headers. On Unix systyems, the _xxx functions are never defined (though there may be a couple of exceptions) so we don't use MSVCRT() for readability's sake. But if you find a system where there is a conflict, then it's best to just systematically use MSVCRT() than to use ifdefs that make it even harder to read. -- Francois Gouget fgouget(a)free.fr http://fgouget.free.fr/ Any sufficiently advanced Operating System is indistinguishable from Linux

1 0

dos console apps question
by Chris Morgan 30 Jul '02

30 Jul '02

Lately I've been trying to get some dos console apps running under wine. These apps run great under wineconsole but not so much just under wine due to the lack of a server side console for the routines in dlls/msdos/vga.c to output too. So, after poking all around it seems that at some point during the normal loading of an app that we should be calling out to the server with alloc_console to create a default console, and binding this console to the current terminal. Does anyone have any suggestions about this? What function this should be done in? Thanks, Chris

4 3

Re: Toolbar redraw problem
by Dusan Vujosevic 30 Jul '02

30 Jul '02

I will add a bit later today it and put in the test app as well. Thanks, D. > > >---- Original Message ---- >From: galberte(a)neo.lrun.com >To: dusanv(a)cadlink.com, wine-devel(a)winehq.com >Subject: Re: Toolbar redraw problem >Date: Mon, 29 Jul 2002 21:09:06 -0400 > >> >>----- Original Message ----- >>From: "dusanv" <dusanv(a)cadlink.com> >>To: "wine-devel" <wine-devel(a)winehq.com> >>Sent: Monday, July 29, 2002 4:27 PM >>Subject: Toolbar redraw problem >> >> >>> Hi, >>> >>> I am seeing a bunch of apps have redrawing problems when a toolbar >is >>> dragged accross the window. Here's a screen shot: >>> >>> http://dusanv.net/files/wine-ss.png >>> >>> Does anyone have any info on this? I'd like to fix it but can't >find >>> anyhting relevant. >>> >> >>Could you please create a bug in Wine's Bugzilla >http://bugs.winehq.com/. >> >>And if that is a test program, that would be good to ad also. I >suspect that >>somewhere during the drag operation, the rectangle invalidated does >not >>contain the edges. It will be fun to find. >> >>Thanks, >>Guy >> >> >> >>

1 0

Re: Re: dos console apps question
by chrismorgan＠rcn.com 30 Jul '02

30 Jul '02

> > From: Eric Pouech <eric.pouech(a)wanadoo.fr> > Date: 2002/07/29 Mon PM 12:34:11 EDT > To: Chris Morgan <cmorgan(a)alum.wpi.edu>, Jukka Heinonen <jhei(a)iki.fi>, > DanKegel <dank(a)kegel.com> > CC: wine-devel(a)winehq.com > Subject: Re: dos console apps question > > Chris Morgan a écrit : > > > > Lately I've been trying to get some dos console apps running under wine. > > These apps run great under wineconsole but not so much just under wine due to > > the lack of a server side console for the routines in dlls/msdos/vga.c to > > output too. So, after poking all around it seems that at some point during > > the normal loading of an app that we should be calling out to the server with > > alloc_console to create a default console, and binding this console to the > > current terminal. Does anyone have any suggestions about this? What > > function this should be done in? > > I don't think this is needed... normally, a program doesn't have to deal > with the creation of it's console > it's up to its parent > > however, what you're facing right now is running a DOS program directly > from the unix prompt (like wine mydospgm.com) > in this case, there is no way for the parent process to tell something > to its child, you it's up to you to do it by running the program with > wineconsole mydospgm.com > the only programs so far that may have to deal with creating a console > are: > - wcmd (but in fact it could deal with the current one) > - winedbg because we don't want the debugger to mix it's output with the > debuggee's one > > maybe something that will be done when the process creation bits are > done is as follows: > - the wine (or winewrapper) will just parse the unix parameters and then > call CreateProcess to spawn the child process > - this wine executable could then be in charge (if the process requested > for execution is a CUI process) to allocate a new console and ask > CreateProcess to make the child process inherit it. > - however, this scheme must also deal with the situation where we want > the child process to either use the current unix shell (btw, I have a > working version of wineconsole using (n)curses which does just that > (1)), or be retargeted to /dev/null (for example) > - in any case, we will need some more parameters to be giving at the > starting time (and yes, this could also be a per app setting in the > registry) > > (1): what's currently missing is a clean way to choose in wineconsole > between the (well known) windows (GDI/USER) version and (not yet > committed) (n)curse for display > > A+ > > Having the process use the current term window is exactly what I'm looking for. How far along is the patch you have and would you be in need of any assistance? I'm not sure what you mean by not being able to have the parent process communicate with the child process and how this affects things. Is the problem how to capture and render the output from the application that was directed to the console and the standard handles? Couldn't this just be done in the appropriate win32 console functions for input/output and with standard unix handles passed around for stdio? Thanks, Chris

2 1

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

wine-devel