March 2009 - Wine-Devel - list.winehq.org

winetricks:

by Rico Schüller

Hi, this patch let winetricks only overwrite d3dx9_36.dll, because all other d3dx9_xx.dlls should be redirected by wine's implementation, so this shouldn't be needed for this dlls. Cheers Rico

March 29, 2009

winetricks: update d3dx redist package.

by Rico Schüller

Hi, this patch updates the DirectX redist package in winetricks to version Mar09. Cheers Rico

March 29, 2009

Re: [RFC] Port of Stefan Dösinger's ARB_vertex_program fixed-function vertex pipeline replacement to 1.1.18

by Henri Verbeet

2009/3/29 Paul TBBle Hampson <Paul.Hampson(a)pobox.com>: > fixme:d3d_surface:surface_upload_data >>>>>>>>>>>>>>>>> GL_INVALID_VALUE (0x501) from glTexSubImage2D @ ../../../dlls/wined3d/surface.c / 349 These are a problem, I think. 2009/3/29 Stefan Dösinger <stefandoesinger(a)gmx.at>: > Its probably a reasonable goal to get this in, but disabled by default until > the performance problems are resolved(I guess that lighting is the main > bottleneck). That will make it easier for others to implement vertex blending > in a proper fashion. > > That said, I don't really remember the state of the code, and if it is clean > enough to be committed. > It will need some work, but I think getting it merged is a good idea.

March 29, 2009

Re: [RFC] Port of Stefan Dösinger's ARB_vertex_program fixed-function vertex pipeline replacement to 1.1.18

by Stefan Dösinger

Am Sonntag, 29. März 2009 06:39:38 schrieb Paul TBBle Hampson: > As before, the code is entirely Stefans, but bugs may certainly have > been introduced by me. Since it now passes the unit tests, it might be > reasonable to actually consider this for mainline, with a registry key > or env var to force a specific choice of fixed-function vertex pipeline. Its probably a reasonable goal to get this in, but disabled by default until the performance problems are resolved(I guess that lighting is the main bottleneck). That will make it easier for others to implement vertex blending in a proper fashion. That said, I don't really remember the state of the code, and if it is clean enough to be committed.

March 29, 2009

Re: wined3d [try 2]: SetDepthStencilSurface is always called when AutoDepethStencilBuffer is enabled

by Henri Verbeet

2009/3/28 Stefan Dösinger <stefandoesinger(a)gmx.at>: > Am Samstag, 28. März 2009 14:58:28 schrieb Stefan Dösinger: >> Am Samstag, 28. März 2009 14:39:15 schrieb David Adam: >> > + hrc = IWineD3DDeviceImpl_CreateSurface(iface, >> > ... >> > + This->parent); >> You'll have to use a callback function similarly to the CreateDevice >> callback to tell d3d8 / d3d9 to create one of their surface structures and >> call wined3d to create a wined3d surface. > Actually, the code changed a little. You'll have to use > IWineD3DDeviceParent_CreateSurface I think > For consistency IWineD3DDeviceParent_CreateDepthStencilSurface() would be best.

March 29, 2009

Re: mciqtz32: Implement driver messages

by Christian Costa

There are some discrepancies in the indentation and I don't mind removing tabs but what's wrong with them, they are commonly use in wine depending on one's taste. Christian Detlef Riekenberg a écrit : > On Sa, 2009-03-28 at 11:48 +0100, Christian Costa wrote: > > Thanks for working on this part of Wine. > > >> +/************************************************************************** >> + * MCIAVI_drvClose [internal] >> + */ >> +static DWORD MCIQTZ_drvClose(DWORD dwDevID) >> +{ >> > > With greetings from copy & paste: > There is no need to fix the MCIAVI != MCIQTZ mismatch in a second Patch. > Fix it here, when you add the code. > > You use TAB in the comments and also in the Code. > Don't do that. > > >

March 29, 2009

Re: How to "bottle" applications for distribution with wine?

by Ben Klein

2009/3/29 Tim Felgentreff <timfelgentreff(a)gmail.com>: > King InuYasha <ngompa13(a)gmail.com> wrote: >> Hello, >> I was working on setting up a Windows game to work on all the Linux machines >> I have, but I don't want to install the full blown Wine on each one. Is >> there a way to "bottle" Wine with application binaries and make it all work >> from a single folder and have it totally self sufficient (similar to >> TransGaming's Cedega for Linux with EVE Online)? > > Sure, you can just copy the full wine install into the wineprefix you created > for your game, e.g. I usually put a "wine" folder next to the drive_c into my > wine prefix for that. Then just make yourself a startup script for you game in > which you set you PATH to search "$WINEPREFIX/wine/bin" first. This is > basically how PlayOnLinux does it. > Hope that helps He's asking if it's possible to bundle a minimal Wine with some native app (e.g. EVE "Linux version" which was EVE for Windows with Cedega, and the same basic principle for the "Linux version" of the Sims shipped with some Mandrakes). The only thing I can think of is to calculate the maximum set of required DLLs for the application, and only ship those, but it's probably not worth it. It's better in general to use a system-wide Wine, due to the general-purpose nature of Wine.

March 29, 2009

Re: How to "bottle" applications for distribution with wine?

by Tim Felgentreff

King InuYasha <ngompa13(a)gmail.com> wrote: > Hello, > I was working on setting up a Windows game to work on all the Linux machines > I have, but I don't want to install the full blown Wine on each one. Is > there a way to "bottle" Wine with application binaries and make it all work > from a single folder and have it totally self sufficient (similar to > TransGaming's Cedega for Linux with EVE Online)? Sure, you can just copy the full wine install into the wineprefix you created for your game, e.g. I usually put a "wine" folder next to the drive_c into my wine prefix for that. Then just make yourself a startup script for you game in which you set you PATH to search "$WINEPREFIX/wine/bin" first. This is basically how PlayOnLinux does it. Hope that helps -Tim

March 29, 2009

Re: mciqtz32: Add basic play capability

by Detlef Riekenberg

On Sa, 2009-03-28 at 16:36 +0100, Christian Costa wrote: > + hr = CoCreateInstance(&CLSID_FilterGraph, NULL, > CLSCTX_INPROC_SERVER, &IID_IGraphBuilder, (LPVOID*)&wma->pgraph); > + if (FAILED(hr)) { > + TRACE("Cannot create filtergraph (hr = %x)\n", hr); > + return MCIERR_INTERNAL; > + } Again TABs in the Code. > + > + hr = IGraphBuilder_QueryInterface(wma->pgraph, > &IID_IMediaControl, (LPVOID*)&wma->pmctrl); > + if (FAILED(hr)) { > + TRACE("Cannot get IMediaControl interface (hr = %x)\n", hr); > + return MCIERR_INTERNAL; TAB again. And while i read this quote: You leak wma->pmctrl here. -- By by ... Detlef

March 29, 2009

Re: mciqtz32: Implement driver messages

by Detlef Riekenberg

On Sa, 2009-03-28 at 11:48 +0100, Christian Costa wrote: Thanks for working on this part of Wine. > +/************************************************************************** > + * MCIAVI_drvClose [internal] > + */ > +static DWORD MCIQTZ_drvClose(DWORD dwDevID) > +{ With greetings from copy & paste: There is no need to fix the MCIAVI != MCIQTZ mismatch in a second Patch. Fix it here, when you add the code. You use TAB in the comments and also in the Code. Don't do that. -- By by ... Detlef

March 29, 2009