wine-devel March 2004

wine-devel@winehq.org

128 participants
264 discussions

Patch Status Check
by Mike Kost 05 Mar '04

05 Mar '04

Alexandre, Can you report on the status of the following patches. I havn't spotted them in CVS and they've been out there for almost 2 weeks now. Austerlitz patch #1 - play audio file with + in filename http://www.winehq.org/hypermail/wine-patches/2004/02/0287.html Austerlitz patch #2 - Calculate the DIB size http://www.winehq.org/hypermail/wine-patches/2004/02/0286.html The patches were tested and appear to solve bug #2011 http://bugs.winehq.org/show_bug.cgi?id=2011 Mike Kost mike at tashcorp dot net

2 1

Re: Fix for programs that store VirtualQueryEx results in signed integers (eg. The Borland Linker)
by Alexandre Julliard 05 Mar '04

05 Mar '04

Troy Rollo <wine(a)troy.rollo.name> writes: > + * The problem with emulating this is that on Linux the top of the stack is at > + * 0xbfffffff and below, so reserving even the balance of this range would > + * artificially limit stack growth. We could move the stack, but it's too late > + * to do that here because there will be pointers to things on the stack > + * that will be affected - moving the stack would need to be done in main() in > + * loader/main.c, which would then be responsible for moving it back (this would > + * be done with mremap and subsequent adjustment to the stack pointer). Actually we don't run on the main stack, so allocating the space above 0x80000000 would definitely be possible, the stack doesn't need to grow there. -- Alexandre Julliard julliard(a)winehq.org

3 8

WinCE application support for WINE and ReactOS
by Steven Edwards 04 Mar '04

04 Mar '04

Hello All, This is all very experimental. I am working on in the ReactOS tree and it might not even work for larger apps but I am happy with the results so far. I was thinking the other day that ReactOS and WINE/Linux might get a big boost if we can push support in the embedded enviroment so I started taking a look at WinCE and Microsoft Embedded Visual C++ 4.0 .BTW: Its a free download now. http://www.microsoft.com/downloads/details.aspx?FamilyID=1dacdb3d-50d1-41b2… I started looking at WinCE and thought it would be nice if we could be source compatible with WinCE apps and binary compatbile on x86. Well it seems that WinCE apps dont differ much from standard Win32 apps execpt the subsystem ID is differnt. If you attempt to run a WinCE application on Windows it will say that its not able to run. Ok no problem, we just run "editbin /subsystem:windows blah.exe" and check it out. Now the app is looking for coredll.dll. No problem there I have created a stub coredll.dll that just forwards all calls to the proper Win32 dlls such as user32, kernel32, etc..... .....and check it out. My little messagebox test works on Windows. Ok soon then I go and run the same test on ReactOS but this time I run a copy of messagebox without changing the subsystem ID...Hey what do you know. It works =). I talked with Alexandre about it a bit and he said that WINE like ReactOS also shouldnt care about the subsystem ID so if someone is interested in testing just drop the messagebox programs and coredll.dll in to a directory and give it a shot. I am having trouble getting more complex apps (hello world) to work atm so I think i am just going to take a break and clear my head for a few days. Some of the WinCE API and Win32 is not 100% compatible so we cant just forward all parts to the Win32 implementation but I think we can do it for most of it. If anyone is interested in helping out the source is in the ROS CVS tree and attached to this email...... binary.zip messagebox.exe - wince messagebox program msgbox.exe - wince messagebox program with subsystem id changed to Windows. wincehel.exe - Hello World WinCE app wincehelw.exe - Hello World WinCE app with subsystem id changed to Windows. coredll.dll - WinCE Win32 API commctl.dll - WInCE common controls API. source.zip coredll - dummy forwarder dll commctl - dummy stub dll for common controls Thanks Steven __________________________________ Do you Yahoo!? Yahoo! Search - Find what you�re looking for faster http://search.yahoo.com

1 0

WinCE application support for WINE and ReactOS
by Steven Edwards 04 Mar '04

04 Mar '04

1 0

Re: Make icon extraction for 16 bit icons work
by Alexandre Julliard 04 Mar '04

04 Mar '04

Dmitry Timoshkov <dmitry(a)baikal.ru> writes: > Changelog: > Martin Pilka <mpilka(a)codeweavers.com> > Make icon extraction for 16 bit icons work. This should really be done with PrivateExtractIcons instead of adding more 16-bit dependencies in our Winelib apps. -- Alexandre Julliard julliard(a)winehq.org

1 0

Re: run authenticated over a NT domain aplications
by Juan Lang 04 Mar '04

04 Mar '04

Hi Marco, Marco escribio: > Hi , > i'm traying to run with wine a legacy aplication that > needs to be run by > a loged in user under NT Domain. That aplication > needs to be > authenticated on the server to access the SQL server. > Looking on google > i've found a post about logonUser patch from Martin > Wilks (snip) > Whi this patch was removed from the > development? Are you sure this patch solves the problem for you? Have you tried the application? What errors do you get? If the patch works, you can apply it to wine yourself and use your copy of wine. You can try resubmitting it to wine-patches and see what AJ says :) > Is there any other way to run aplications of those? The application queries SQL server? It may be possible to run the SQL server ODBC drivers; try doing a google search for this. Boaz Harrosh reported some success using the MS ODBC driver manager in Wine, see this thread: http://www.winehq.org/hypermail/wine-devel/2004/01/0466.html Good luck, --Juan __________________________________ Do you Yahoo!? Yahoo! Search - Find what you�re looking for faster http://search.yahoo.com

1 0

Fwd: Fw: New setupapi stuff
by Steven Edwards 04 Mar '04

04 Mar '04

I am not going to have a chance to merge this. We have fixed a few more minor bugs in InstallHInfSection. Thanks Steven Note: forwarded message attached. __________________________________ Do you Yahoo!? Yahoo! Search - Find what you�re looking for faster http://search.yahoo.com

1 0

(no subject)
by Ivan Leo Murray-Smith 04 Mar '04

04 Mar '04

The email http://www.winehq.com/hypermail/wine-patches/2004/03/0032.html contains a zip attachment, that contains a .scr file, chances are it's a virus. If it is, please remove it from the archive. Ivan.

1 0

Office '97 test: installer good, app not usable
by Dan Kegel 04 Mar '04

04 Mar '04

A friend wanted to borrow my old laptop while she's in the hospital, so I scurried around and got wvdial and fvwm95 working on my old 133MHz 48MB RAM, 1.1GB disk Redhat 6.2 laptop, then built the latest Wine. Ran into two minor problems, but basically it built just fine. Took all night, but hey, what do you expect for a 133MHz laptop? Then the real test: Office '97. The installer worked very, very well. Only flaw was some letters were cut off on the right hand side of the pacifier dialogs during install. This is the best I've seen it in the four or five years I've been trying this. Running Office was another matter. I only tested it a bit, but there's a display problem: text is displayed invisible in the main document pane on the same line you're editing. If you refresh, everything's there. Not terribly usable. Sigh. I guess I'll dig up the copy of Crossover I bought for testing a while ago. Wonder if that even works with such an old Linux, though... - Dan -- My technical stuff: http://kegel.com My politics: see http://www.misleader.org for examples of why I'm for regime change

4 4

RE: wine/ objects/dc.c dlls/x11drv/x11drv.spec dll ...
by Robert Shearman 04 Mar '04

04 Mar '04

> > Log message: > Changed the CreateDC driver entry point to use an HDC > instead of a DC > pointer. > > Patch: http://cvs.winehq.org/patch.py?id=11356 > > Old revision New revision Changes Path > 1.56 1.57 +1 -1 wine/dlls/x11drv/x11drv.spec > 1.26 1.27 +1 -1 wine/dlls/wineps/wineps.spec > 1.34 1.35 +1 -1 wine/dlls/ttydrv/ttydrv.spec [...] Why change the prototypes in the .spec files? The first parameter is still a pointer, even if it is now void* instead of DC*. Rob

2 1

tests for winsock and msvcrt won't link
by Dan Kegel 04 Mar '04

04 Mar '04

I updated to CVS yesterday, and now I get an error when building wine, namely: winsock and msvcrt tests won't link because they can't find accept and feof, respectively. Commenting out the SUBDIRS= lines in those two DLLs' Makefiles got me past it (I think; it's still building). This problem was not present in the most recent snapshot. - Dan -- My technical stuff: http://kegel.com My politics: see http://www.misleader.org for examples of why I'm for regime change

3 4

avi file save is not work.
by kscho 04 Mar '04

04 Mar '04

Hi! when i test wine-20040121 , it works fine. but wine-2040213 is not work. the function of AVIMakeCompressedStream is not returned AVRERR_OK . i tested each dlls(avifil32.dl.so, ntdll.dll.so,...). finally i found i replace kernel32.dll.so(in the wine-20040121) it works fine. How I can do it ? Thanks in advance

2 1

X11DRV_GLX_CreateDriver
by Maurizio Monge 04 Mar '04

04 Mar '04

Hi, if found a commented X11DRV_GLX_CreateDriver in the x11drv dll, did anyone try to write a glx backend and stopped for some reason? I was just planning to write a OpenGL backend for directdraw (i.e. using glDrawPixels, etc), as i think it would be almost as fast as dga and far more stable, but does anyone think it would be a bad idea? Thanx Maurizio

3 2

want to debug winemine
by Guruprasad B. B. 04 Mar '04

04 Mar '04

Hi, i copied winemine source to a separate directory (winemine2) then i compiled winemine2 using winemaker. it created a shared object file (winemine2.exe.so). i am able to launch winemine2 application fine. what i want to do is debug the winemine source code.. say, i want to set a breakpoint in main.c( part of winemine source code) i can't do that unless i have a winemine2.exe. please help me figure out a way to debug this compiled source code thanks Guruprasad ********************************************************************* Disclaimer: The information in this e-mail and any attachments is confidential / privileged. It is intended solely for the addressee or addressees. If you are not the addressee indicated in this message, you may not copy or deliver this message to anyone. In such case, you should destroy this message and kindly notify the sender by reply email. Please advise immediately if you or your employer does not consent to Internet email for messages of this kind. *********************************************************************

1 0

WineHQ: fix some nasty problems in TODO
by Dimitrie O. Paun 04 Mar '04

04 Mar '04

This one is fairly high importance, the page looks rather crappy ATM. My bad, sorry for the mess. ChangeLog Properly finish the <a> tags marking the sections. -- Dimi. Index: templates/en/todo_lists.template =================================================================== RCS file: /home/wine/lostwages/templates/en/todo_lists.template,v retrieving revision 1.26 diff -u -r1.26 todo_lists.template --- templates/en/todo_lists.template 3 Mar 2004 19:34:28 -0000 1.26 +++ templates/en/todo_lists.template 4 Mar 2004 05:18:45 -0000 @@ -287,7 +287,7 @@ </ol> - <a name="ui"><h3> D. User Interface </h3> + <a name="ui"></a><h3> D. User Interface </h3> <ol> <li> Visible region handling in server <span class=inprogress>[IN PROGRESS]</span> <ul> @@ -305,7 +305,7 @@ </ol> - <a name="formats"><h3> E. File Formats </h3> + <a name="formats"></a><h3> E. File Formats </h3> <ol> <li> Finalize the .spec file format <span class=done>[DONE]</span> <ul> @@ -328,7 +328,7 @@ </ol> - <a name="api"><h3> F. Exported API </h3> + <a name="api"></a><h3> F. Exported API </h3> <ol> <li> Finish DLL separation Phase 1 <span class=done>[DONE]</span> <ul> @@ -353,7 +353,7 @@ </ol> - <a name="tools"><h3> G. Tools </h3> + <a name="tools"></a><h3> G. Tools </h3> <ol> <li> Winebuild: build DLLs from .def files <span class=done>[DONE]</span> <ul> @@ -412,7 +412,7 @@ </ol> - <a name="misc"><h3> H. Miscellaneous </h3> + <a name="misc"></a><h3> H. Miscellaneous </h3> <ol> <li> Testing daemon to run as a Windows service <span class=inprogress>[IN PROGRESS]</span> <ul> @@ -454,7 +454,7 @@ </ol> - <a name="code"><h3> I. Source Code </h3> + <a name="code"></a><h3> I. Source Code </h3> <ol> <li> Move controls/*, windows/* -> dlls/user/ <span class=inprogress>[IN PROGRESS]</span> <ul>

1 0

kernel32.dll.so isn't work with video for window(AVIMakeCompressedStream)
by kscho 04 Mar '04

04 Mar '04

Hi~, I runed avi related program work with wine-20040121, It works fine. thanks this~ but I tested wine-20040213, AVIMakeCompressedStream isn't work properly, therefore not returned GetAvailableSystemCodec in my function. below is my test code. when i replace kernel32.dll.so (in the wine-20040121) it works. How can I do? thanks in advance -----------------------my test code ------------------------------ #define AVIIF_KEYFRAME 0x00000010L // this frame is a key frame. static const struct tREC_FOURCC{ FOURCC fcc; char *name; } recommended_fcc[] = { { mmioFOURCC('m','p','4','3'), "mpeg4_3" }, // Microsoft MPEG4 V3 { mmioFOURCC('m','p','4','2'), "mpeg4_2" }, // Microsoft MPEG4 V2 { mmioFOURCC('d','i','v','x'), "divx" }, { mmioFOURCC('I','V','5','0'), "indeo_5" }, { mmioFOURCC('I','V','4','0'), "indeo_4" }, }; static char empty_audio_frame[SAMPLED_SMSIZE_8*4]; BOOL GetAvailableSystemCodec(PAVIWRITER paw) { int i; if(paw->ip.flags & AW_CODEC_FORCCC) { paw->opts.fccHandler = paw->ip.codecFourcc; paw->codec_name = NULL; if(AVIERR_OK == AVIMakeCompressedStream(&paw->psCompressed, paw->ps, &paw->opts, NULL)) { return TRUE; } } memset(&paw->opts, 0, sizeof(paw->opts)); for(i=0; i<sizeof(recommended_fcc)/sizeof(struct tREC_FOURCC); i++) { paw->opts.fccHandler = recommended_fcc[i].fcc; paw->codec_name = recommended_fcc[i].name; if(AVIERR_OK == AVIMakeCompressedStream(&paw->psCompressed, paw->ps, &paw->opts, NULL)) { return TRUE; } } return FALSE; }

1 0

run authenticated over a NT domain aplications
by Marco Rodriguez M. 03 Mar '04

03 Mar '04

Hi , i'm traying to run with wine a legacy aplication that needs to be run by a loged in user under NT Domain. That aplication needs to be authenticated on the server to access the SQL server. Looking on google i've found a post about logonUser patch from Martin Wilks ( http://www.winehq.org/hypermail/wine-patches/2002/11/0110.html) that works with pam and winbind. Whi this patch was removed from the development? Is there any other way to run aplications of those? Are there some one who can help me to or have a tutorial or a HOWTO to run this kind of aplications? Or maybe i'ts imposible for now.... i hope not, this is very improtant to completely migrate propietary aplication an legacy sistem to O.S. T.I.A. -- Marco Rodriguez M. marco[(a)]ubiobio.cl U. Bio Bio Concepcion Chile

1 0

Re: Re: Native NetBSD audio driver
by wine＠frotz.org 03 Mar '04

03 Mar '04

> What is the plan for combining these audio drivers? One thing that is common > to each driver are the functions that handle the wave headers, adding, > removing > etc. I understand the desire to extract common code from drivers that have largely been cut and paste from the OSS driver's boilerplate, but I hope this merge won't restrict new drivers to an implementation that uses this boilerplate. I'm developing from the ground up a new ALSA/OpenAL driver which I intend to provide a "best quality" PCM DirectSound experience for gaming. The driver uses ALSA's DMIX plugin device, so it should interoperate with similarly configured arts, jack, etc. servers. It supports secondary buffers and 3D. The intent is to take advantage of HW support for these features when available. As yet I have had no need to reuse code from the OSS driver. Legacy waveOut/ waveIn interfaces will be implemented using the driver's DirectSound interfaces. The driver is very pre-alpha and development is admittedly very slow. However, when it is ready -- if there is interest -- I would like to post it to wine-patches for code review and addition to CVS. --d

1 0

ImmAssociateContextEx missing
by Jesse Allen 03 Mar '04

03 Mar '04

Hi, I have noticed that when you load up Warcraft III, and then quit the game, that it will pop up with a messagebox error message complaining about a memory location, 0xdeadbeef. I have also noticed this message: err:win32:PE_fixup_imports No implementation for imm32.dll.2(ImmAssociateContextEx) imported from C:\war3\war3.exe, setting to 0xdeadbeef I looked for ImmAssociateContextEx in imm32, and its not there, not even in the imm32.spec file. I implemented a stub for ImmAssociateContextEx, and then ran the game. It now comes up with my stub message upon exiting the game: fixme:imm:ImmAssociateContextEx (0x20021, (nil), 16): stub So apparently war3.exe has a reference to ImmAssociateContextEx, and detects the bad address, and immediately exits with an error. Applying the patch allows the game to exit normally. I have the patch attached. Any comments? Jesse --- wine/dlls/imm32/imm.c 2004-03-02 13:55:57.000000000 -0700 +++ wine-new/dlls/imm32/imm.c 2004-03-02 16:49:23.000000000 -0700 @@ -255,6 +255,15 @@ } /*********************************************************************** + * ImmAssociateContextEx (IMM32.@) + */ +BOOL WINAPI ImmAssociateContextEx(HWND hWnd, HIMC hIMC, DWORD dwFlags) +{ + FIXME("(%p, %p, %ld): stub\n", hWnd, hIMC, dwFlags); + return FALSE; +} + +/*********************************************************************** * ImmConfigureIMEA (IMM32.@) */ BOOL WINAPI ImmConfigureIMEA( --- wine/dlls/imm32/imm32.spec 2004-02-02 17:12:03.000000000 -0700 +++ wine-new/dlls/imm32/imm32.spec 2004-03-02 16:21:47.000000000 -0700 @@ -1,4 +1,5 @@ @ stdcall ImmAssociateContext(long long) +@ stdcall ImmAssociateContextEx(long long long) @ stdcall ImmConfigureIMEA(long long long ptr) @ stdcall ImmConfigureIMEW(long long long ptr) @ stdcall ImmCreateContext()

2 1

Re: Native NetBSD audio driver
by Yorick Hardy 03 Mar '04

03 Mar '04

I started now with the integration of the OSS and NetBSD audio drivers. Before I get too far, I would like to hear suggestions/criticisms. 1) I created the directory dlls/winmm/drvcommon (perhaps there is a better name ?) 2) moved dlls/winmm/wineoss/oss.c and dlls/winmm/winenbsd/nbsd.c to the single integrated file dlls/winmm/drvcommon/drv.c. 3) renamed the files dlls/winmm/wineoss/oss.h and dlls/winmm/winenbsd/nbsd.h to dlls/winmm/wineoss/drv.h and dlls/winmm/winenbsd/drv.h respectively. 4) Update the respective Makefile.in to use the integrated dlls/winmm/drvcommon/drv.c The idea is that eventually winenbsd and wineoss only have the drv.h and the spec file. drv.h will define all driver specific names/functions. I must stress that I am only concerned with the OSS and NetBSD drivers at the moment. Is this too much? Or can someone suggest a better solution? Kind regards, -- Yorick Hardy Tel: +2711 489 3640 | Fax: +2711 489 2067 | Office: C-Ring 517 Auckland Park Campus | Rand Afrikaans University | South Africa Department of Applied Mathematics : http://general.rau.ac.za/apm Standard Bank Academy for Information Technology : http://csweb.rau.ac.za

3 3

Re: SysParametersInfoW->A crosscall (fixed)
by tony_lambregts＠telusplanet.net 03 Mar '04

03 Mar '04

Alexandre, is there any reason that this patch isn't applied? http://www.winehq.org/hypermail/wine-patches/2004/02/0332.html -- Tony Lambregts

2 1

Re: winemaker fixes
by Dimitrie O. Paun 02 Mar '04

02 Mar '04

On Tue, 2 Mar 2004, Francois Gouget wrote: > winemaker is pretty broken since it has been patched to call winegcc. I > suspect it was not tested. Hey, I can't do everything! :))) I just wanted to get the ball rolling. > We must specify '-lmsvcrt' if using the msvcrt. Please don't, it's not needed. If you want to use msvcrt, please pass the -mno-cygwin switch. if that doesn' work, it's a bug in winegcc. > There is still work to do: > > 1. Linking with uuid is broken. I suspect winegcc finds the Unix > /lib/libuuid.so first and links with that instead of with our libuuid.a > library. That shouldn't happen. Can you please run winegcc with the -v flag, and send the output my way please? > 2. wrc does not find 'windows.h' (yes, some RC files #include Win32 > headers). wrc should know about the location of the headers like winegcc > (since our Makefile don't know anything about where the Wine headers are > anymore). I've verified the source and it should. Maybe you can produce a --debug=FF trace? > 4. We have lost the autoconf integration. We should encapsulate our macros so they can conveniently be used by people in their configure.ac scripts. I think that's the proper way to get autoconf integration. > 5. Nothing works if Wine has not been installed. This is quite > impractical for Wine developers. It's true, but there are many reasons you need to install Wine to be able to use Winelib. I doubt it will change in the near future. > 6. winegcc is not rebuilt if the '--prefix' changes. Maybe AJ can fix the Makefile. I think winegcc.o should depend on the Makefile. > 7. Building dlls does not work yet but that was expected and Dimi is > working on it. In progress :) -- Dimi.

3 2

Re: Native NetBSD audio driver
by Eric Pouech 02 Mar '04

02 Mar '04

Yorick Hardy a écrit : > This patch adds the audio driver winenbsd using the native NetBSD > audio system as an alternative to OSS. On the one hand > this is useful to directly make use of the features of the NetBSD > audio system instead of using emulation, on the other hand > it is another driver to maintain and is quite close to the wineoss driver. > If the driver is accepted, I think the NetBSD support for wineoss > should remain for testing and for the main driver. I really think we're starting to create a real mess for the audio drivers. It's always useful to have drivers access the HW at the lowest level, so we should support NetBSD. However, if the iface is rather close to OSS, I'd rather suggest we try to integrate all the drivers with the same features into a single piece of driver > diff -urN /home/yorick/software/wine/wine/dlls/Makefile.in ./dlls/Makefile.in > --- /home/yorick/software/wine/wine/dlls/Makefile.in Sat Feb 14 19:20:00 2004 > +++ ./dlls/Makefile.in Sat Feb 21 23:43:35 2004 > @@ -1745,6 +1749,7 @@ > winmm/winejack/winejack.drv$(DLLEXT): winmm/winejack > msacm/winemp3/winemp3.acm$(DLLEXT): msacm/winemp3 > winmm/winenas/winenas.drv$(DLLEXT): winmm/winenas > +winmm/winenas/winenbsd.drv$(DLLEXT): winmm/winenbsd *** this should be winenbsd A+

7 8

Cross compiling Wine with MinGW
by Hans Leidekker 02 Mar '04

02 Mar '04

Hi, I spent some time cross compiling all of Wine with MinGW according to this recipe: http://winehq.com/?issue=123#Cross-compiling Wine and I thought you might be interested in the results. I can report a bug in Wine's makefiles right away: having those vxd's in subdirectories that end in .vxd causes make to barf on targets like this one: ifsmgr.vxd$(DLLEXT): ifsmgr.vxd/ifsmgr.vxd$(DLLEXT) $(RM) $@ && $(LN_S) ifsmgr.vxd/ifsmgr.vxd$(DLLEXT) $@ because, if $(DLLEXT) is empty, it will try to create a link with a name that's already there as a directory. Of all dlls these don't compile: x11drv kernel32 gdi32 ws2_32 comctl32 icmp iphlapi msvcrt ntdll rpcrt4 shlwapi vnb.vxd wininet wsock32 x11drv, kernel32, gdi32 and ntdll being predictable, because they build directly on X11 and Unix API's. Same goes for the networking related dlls (ws2_32, icmp and iphlpapi, vnb.vxd, wininet, wsock32). msvcrt is close to building because what I saw was mostly header clashes, which could be fixed with proper guards I think. rpcrt4 fails because it uses one Unix API, gettimeofday, and both comctl32 and shlwapi suffer from the bug in dlltool that Dmitry reported and fixed recently. -Hans

3 3

Re: Re: Native NetBSD audio driver
by chmorgan＠charter.net 02 Mar '04

02 Mar '04

What is the plan for combining these audio drivers? One thing that is common to each driver are the functions that handle the wave headers, adding, removing etc. I'm also weary of any kind of combination that includes OSS as OSS is depreciated and has been replaced by Alsa. I'm also concerned with the arts, jack and nas drivers being left out of this merge. While many of the audio drivers have a lot in common there are a LOT of subtle differences that are necessary for things to work correctly. Maybe Eric and others could comment on what they see as being able to be combined, although I've worked a bit on audio drivers I'm drawing mostly a blank. Thanks, Chris > > From: Yorick Hardy <yha(a)na.rau.ac.za> > Date: 2004/03/02 Tue AM 04:38:41 EST > To: wine-devel(a)winehq.org > CC: yha(a)na.rau.ac.za > Subject: Re: Native NetBSD audio driver > > I started now with the integration of the OSS and NetBSD audio drivers. > Before I get too far, I would like to hear suggestions/criticisms. > > 1) I created the directory dlls/winmm/drvcommon > (perhaps there is a better name ?) > 2) moved dlls/winmm/wineoss/oss.c and dlls/winmm/winenbsd/nbsd.c > to the single integrated file dlls/winmm/drvcommon/drv.c. > 3) renamed the files dlls/winmm/wineoss/oss.h and dlls/winmm/winenbsd/nbsd.h > to dlls/winmm/wineoss/drv.h and dlls/winmm/winenbsd/drv.h respectively. > 4) Update the respective Makefile.in to use the integrated > dlls/winmm/drvcommon/drv.c > > The idea is that eventually winenbsd and wineoss only have the drv.h > and the spec file. drv.h will define all driver specific names/functions. > I must stress that I am only concerned with the OSS and NetBSD drivers > at the moment. > > Is this too much? Or can someone suggest a better solution? > > Kind regards, > > -- > Yorick Hardy > Tel: +2711 489 3640 | Fax: +2711 489 2067 | Office: C-Ring 517 > Auckland Park Campus | Rand Afrikaans University | South Africa > Department of Applied Mathematics : http://general.rau.ac.za/apm > Standard Bank Academy for Information Technology : http://csweb.rau.ac.za > > >

1 0

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 March 2004