Re: [PATCH v2 0/4] MR10967: Prefer builtin for d3d helper libraries.

[Tim Clem (＠tclem)]

On Mon Jun 29 19:04:33 2026 +0000, Nikolay Sivov wrote:
> Otherwise we'll never learn about those issues and it will never get
> fixed. It will be easy to revert for the next major release, if it comes
> to that.
> From this list only ID3DXEffectCompiler looks annoying, because it will
> need substantial amount of changes, to get it right.
> Right, clearly we'd like to find these sorts of issues, but to me it's a question of whose responsibility that is. Do we want to break things widely and at random and let users deal with the frustration? Or should we, the developers, be seeking out games that ship their own d3d libraries and setting builtin overrides to see what happens?
> only ID3DXEffectCompiler looks annoying, because it will need substantial amount of changes, to get it right.

That's the sort of thing I worry about - that's sounds like something that will be broken for a while, which means we're effectively requiring that users tinker with DLL overrides to get something working that used to be fine out-of-the-box.

-- 
https://gitlab.winehq.org/wine/wine/-/merge_requests/10967#note_144462