I tried to work on the patch again, but it does not apply anymore.
I am slowly going through what happened in profile.c, to find out
which changes should be kept,
and which go in a wrong direction.
I stumbled already @the first entry:
commit 9a10234ef2b5212ba44b82a797c478f190b4dad1
Author: Paul V
On Fri, Aug 21, 2009 at 11:17 PM, F Capela wrote:
> I use Wine mostly to play World of Warcraft and I've had a regression in
> World of Warcraft (when running fullscreen inside a virtual desktop and using
> the opengl renderer) with patches from the last two weeks:
>
> - Patch 12d1ff8ef6c34533a20
Hi Jacek,
> Your patch looks good (although I'd suggest splitting set_proxy to two
> function instead of doing it by gotos), but I've just sent a patch that
> makes mshtml use wininet for networking (via urlmon), so your patch is no
> longer needed. My patch is a major step forward in MSHTML/shdoc
Hi Juan,
Your patch looks good (although I'd suggest splitting set_proxy to two
function instead of doing it by gotos), but I've just sent a patch that
makes mshtml use wininet for networking (via urlmon), so your patch is
no longer needed. My patch is a major step forward in MSHTML/shdocvw
i
> I have a windows dll without source code (vendor.dll) that I want to use in
> a winelib application.
>
> 1) Creating a vendor.def file doesn't work. The resulting file has an empty
> EXPORTS section:
>
> winedump spec vendor.dll
> winebuild --def -E vendor.spec -o vendor.def
That seems to mean w
Hi Thomas,
On Sat, Aug 22, 2009 at 2:57 AM, Thomas Trummer wrote:
> I can do that. Just to make sure: The WS_ prefixes only get added to symbols
> which collide with the corresponding linux header files?
Yes, precisely right. Thanks!
--Juan
Thomas Trummer schrieb:
> Hi,
>
> I have a windows dll without source code (vendor.dll) that I want to use
> in a winelib application.
>
> There are two problems however:
>
> 1) Creating a vendor.def file doesn't work. The resulting file has an
> empty EXPORTS section:
>
> winedump spec vendor.
I use Wine mostly to play World of Warcraft and I've had a regression in World
of Warcraft (when running fullscreen inside a virtual desktop and using the
opengl renderer) with patches from the last two weeks:
- Patch 12d1ff8ef6c34533a20008f4cfeb73ee4c601a5d (winex11: Add handling of take
focus
Hi,
OK, a minute after I sent the mail I figured out number two:
For vendor.dll the corresponding .def file has to be called libvendor.def.
I still need help with point one, though.
Thomas
Hi,
I have a windows dll without source code (vendor.dll) that I want to use in
a winelib application.
There are two problems however:
1) Creating a vendor.def file doesn't work. The resulting file has an empty
EXPORTS section:
winedump spec vendor.dll
winebuild --def -E vendor.spec -o vendor.d
Am 21.08.2009 um 23:06 schrieb Matteo Bruni:
I'm trying to follow Juan Lang suggestions on how to structure the D3D
assembler patches. I'm not yet sure on how to proceed with the bulk of
the assembler, however these preparatory patches should be safe.
<0001-d3dx9-Add-D3DXAssembleShader-and-rela
Hi Juan,
I can do that. Just to make sure: The WS_ prefixes only get added to symbols
which collide with the corresponding linux header files? So basically I
create a small test file with
#include
#include
#include "af_irda.h"
and check for collisions. Symbols that don't collide remain unchan
I think it is better to separate the vtables first - ie, give
IDirectDrawSurface4, IDirectDrawSurface2 and IDirectDrawSurface their
own vtable
Also the last iteration of Michael Karcher's patches missed out some
getters, like IDirect3DDevice*::GetRenderTarget. There may be other
function
13 matches
Mail list logo
