Stephen Kitt <sk...@debian.org> writes: > gcc-mingw-w64 ships different variants of libgcc, so it can’t just drop one > in a directory on the default Wine DLL path — Windows programs built with > gcc-mingw-w64 have to ensure that the appropriate DLLs are available > alongside them.
And to be clear, what's a good way to do that? Add the appropriate mingw lib directory to WINEPATH? Is it fine to use a unix filename there, it should it somehow de translated to a windows file name? (For my use case, I'd prefer not copying the dll into the same directory as the executable, even though that's probably the way to go if I were to distribute executables to others). > What *is* possible is that previous versions of the compiler didn’t > produce binaries needing libgcc in as many cases, so you might end up > with a binary which just works whereas now you don’t. Ah, that's possible, in particular, since I'm not sure if my earlier use involved C++ at all. >> * The strace output also shows that wine attempts to open >> "/usr/lib/wine/../i386-linux-gnu/wine/./%1.dll.so" Out of curiosity, is there a good reason for this? Regards, /Niels -- Niels Möller. PGP key CB4962D070D77D7FCB8BA36271D8F1FF368C6677. Internet email is subject to wholesale government surveillance.
