- Wine-Devel - list.winehq.org

Re: Native NetBSD audio driver
by Yorick Hardy March 3, 2004

March 3, 2004

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

March 3, 2004

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

March 2, 2004

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

March 2, 2004

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

March 2, 2004

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

March 2, 2004

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

Re: winegcc: portability
by Kirill Smelkov March 2, 2004

March 2, 2004

1 Март 2004 05:52, Dimitrie O. Paun написал: > OK, this is it. I've included the new config.h.in for > patch review convenience. Please run > > autoheader > autoconf > > after applying it. With this stuff in the tree, we should > be able to build programs/* with it. Next on the list is > -shared support... > > ChangeLog > Instrument winegcc to use the compilers and options detected > at configure time. Add support for parsing/formatting a string > array from/to a char string. Add option to disable short wchar > support in winegcc. And what about next (removed from winemaker by your recent patch) -fpermissive, -fms-extensions -fno-for-scope ? They are very handy when porting win32 apps. -- Kirill.

2 3

Re: Cross compiling Wine with MinGW
by Hans Leidekker March 2, 2004

March 2, 2004

On Sunday 29 February 2004 20:49, Juan Lang wrote: > > Shouldn't wininet build on ws2_32 and thus compile? > > I think it should be investigated... > > wininet currently depends on OpenSSL and BSD (unix) > sockets. I think the way OpenSSL is being used makes > it rather hard to use ws2_32 instead, but if someone > wants to take that on that would help. I'm trying to > implement SSL in secur32.dll so wininet can use this, > but it will take me a while (it's rather large). > Helpers welcome :) > > I can fix up vnb.vxd, it really should build on MinGW, > whether or not it's useful to do so. I'll send a > patch shortly. If I include winsock2.h, get rid of the sys/socket.h, netinet/in.h and arpa/inet.h includes and additionally link to ws2_32 it builds on MinGW as well as Wine. > Hans, why didn't wsock32 build? It looks like > configure should protect you against missing headers > and whatnot; it mostly forwards to iphlpapi and > ws2_32. It's missing some constants: ../../../wine/dlls/wsock32/protocol.c:144: `SOCK_STREAM' undeclared (first use in this function) ../../../wine/dlls/wsock32/protocol.c:155: `SOCK_DGRAM' undeclared (first use in this function) These are in winsock.h but protocol.c only includes winsock2.h When I change the include to winsock.h I get: ../../../wine/include/winsock.h:25:4: #error Please use Winsock2 in Wine winsock2.h says: FIXME: Still missing required Winsock 2 definitions. MinGW and MSVC versions of winsock2.h have the defines, so I guess we need to add them. Attached patch does so. -Hans Changelog: add protocol type constants.

2 2

Problems with CHtmlView class in WINE
by vishal wable March 2, 2004

March 2, 2004

Respected Sir, I am trying to run a MFC application in Red Hat Linux 8 using WINE.(Latest Version). I have used a MFC class "CHtmlView" in order to display html pages. Following line of code does that for me. Navigate2( "MyPage.html",NULL,NULL); In WINE i get the following error when trying to do so. "Cannot create an empty document" and the application crashes. Could you please help me to solve this problem. thank you, Regards, Vishal Wable --------------------------------- Do you Yahoo!? Get better spam protection with Yahoo! Mail

2 1

Close button on MFC dockable windows
by Justin Chevrier March 2, 2004

March 2, 2004

Several programs: eg: Powergrab: http://www.cosmicwolf.com SCB Demo3: http://adam.stup.ac.ru/Developer/ ArticleDetail.aspx?ar=318&l=n&mi=10&mic=40 that make use of MFC to do things like dockable windows don't properly draw the close button on docked windows. Instead of an 'x' it looked more like an 'r'. After some investigation and traces I saw that wine was substituting Arial in for Marlett when Marlett was specified with a DEFAULT_CHARSET. I changed the behaviour to instead load 'webdings' when this situation was encountered. This changed the font drawn on the button from an Arial 'r' to a Webding close 'x' character. Unfortunately it was drawn well below the actual button. I am not sure of the correct way to fix this. I have included a changed line: if(ppem <= startsz || ppem > endsz) that corrects this but I doubt it's correct. Justin Chevrier Changelog: Allow MFC programs that dock windows to draw a correct close button. _________________________________________________________________ STOP MORE SPAM with the new MSN 8 and get 2 months FREE* http://join.msn.com/?page=dept/bcomm&pgmarket=en-ca&RU=http%3a%2f%2fjoin.ms…

1 0