When 1.3.19 came out it changed the build requirements for OSS support
-- OSS 3 was no longer supported and OSS 4 dev libraries were required
at build time.
This was the changelog:
New sound driver architecture for MMDevAPI.
Better support for relative mouse events in DInput.
Debugger support for the ARM platform.
Various improvements in D3DX9.
More MSVC runtime functions.
Various bug fixes.
At least two distros broke their OSS support as a result, since the
standard "update wine version but use same packaging" didn't return a
complete Wine anymore. In my case I only noticed when a bug report came
in and I manually looked at the package build log.
This sort of thing would be much less likely to happen if such a build
dependency change were noted in the release notes, such as a "OSS 3 no
longer supported" bullet point.
Thanks,
Scott Ritchie
On Wednesday 01 June 2011 01:38:24 Piotr Pawłow wrote:
> Since commit fadfdf21c055caf833a137ffc269c2073dc87fd6 surface refcounts are
> forwarded to the container. We need to break this forwarding in
> swapchain_init() error path, otherwise the swapchain refcount goes down to
> zero and swapchain_cleanup() gets called on an invalid, partly initialized
> swapchain.
This patch looks OK
The Pathologic demo in bug 21552 expects that the reference count of a
IDirect3D9 instance is incremented after a successful call to
CreateDevice with the instance.
Does my proposed fix for d3d8 and d3d9 manage the reference count of the
device parent appropriately? In particular, I'm concerned about the
slightly cumbersome acquisition of the pointer to the parent instance
within the Release call for the Direct3D device interface. Is the
overall location of the AddRef/Release calls correct, and should I be
doing something differently when the device tries to decrement the
parent reference count?
Hi,
While running your changed tests on Windows, I think I found new failures.
Being a bot and all I'm not very good at pattern recognition, so I might be
wrong, but could you please double-check?
Full results can be found at
http://testbot.winehq.org/JobDetails.pl?Key=11350
Your paranoid android.
=== WVISTAADM (32 bit infosoft) ===
infosoft.c:183: Test failed: failed
infosoft.c:197: Test failed: failed
=== W2K8SE (32 bit infosoft) ===
infosoft.c:183: Test failed: failed
infosoft.c:197: Test failed: failed
=== W7PRO (32 bit infosoft) ===
infosoft.c:183: Test failed: failed
infosoft.c:197: Test failed: failed
=== W7PROX64 (32 bit infosoft) ===
infosoft.c:183: Test failed: failed
infosoft.c:197: Test failed: failed
=== W7PROX64 (64 bit infosoft) ===
infosoft.c:183: Test failed: failed
infosoft.c:197: Test failed: failed
Does the enum_device_entry structure have to be in ddraw_private.h? I think you can just declare it in ddraw.c because it is used only there.
At some point we'll want to get rid of the ddraw device type strings and call wined3d_get_adapter_identifier - but that needs more work and some more tests.
Am 31.05.2011 um 12:50 schrieb Andrew Nguyen:
> ---
> dlls/ddraw/ddraw.c | 43 +++++++++++++------
> dlls/ddraw/ddraw_private.h | 8 ++++
> dlls/ddraw/tests/d3d.c | 98 ++++++++++++++++++++++++++++++++++++++++++++
> 3 files changed, 136 insertions(+), 13 deletions(-)
>
>
> <0004-ddraw-Extend-the-lifetime-of-the-EnumDevices-strings-b.txt>