On Mon Jun 29 20:01:03 2026 +0000, Paul Gofman wrote:
Note also that technically preferring builtin when native should be loaded according to dll path resolution rules is functionally wrong behaviour: it introduces difference between the dll present on disk (at the loaded dll path) and the actual memory image, certain things might be unhappy about that. There are some native dlls which have no chances of working by present design (like native MS d3d dlls) and where there is just no point to load that, but in the other cases (like d3d helper libraries, MSVC runtime libraries) isn't replacing that with builtin is just functionally wrong? I realize that there might be other considerations why preferring builtin might still be making sense, but it seems to me the argument for forcing builtin for the purpose of easier getting aware of builtin bugs is a bit counter-intuitive, it reads to me like adding a hack, and, curiously, with the purpose to break things intentionally.
-- https://gitlab.winehq.org/wine/wine/-/merge_requests/10967#note_144497