Proper way to chain-inject DLLs into wine?

Cláudio Sampaio patola at gmail.com
Wed Jan 6 21:40:12 CST 2021


Thank you for the response, sorry for disturbing the list with non-wine
stuff. I'll do as you suggested.

On Wed, Jan 6, 2021 at 5:14 PM Derek Lesho <dlesho at codeweavers.com> wrote:

> On 1/5/21 7:07 PM, Cláudio Sampaio wrote:
>
> >
> > It acts this way by being put into the executable directory and by
> > itself it calls the functions in the original DirectX dxgi.dll.
>
> Your problem probably lies somewhere else, as this mechanism is already
> fully supported by wine and DXVK when setup correctly. Make sure you are
> installing DXVK through the setup_dxvk.sh script, and not manually
> copying the dlls into the game directory.  This will put DXVK in your
> system dll directory (system32 and syswow64), which the thunk will use.
>
> If you still can't get it to work, it may be good to move this
> discussion to the bug tracker, since as of now it doesn't seem to
> involve wine development discussion.
>
>
>
>

-- 
Cláudio "Patola" Sampaio
MakerLinux Labs - Campinas, SP
Resume <https://github.com/Patola/resume> Gmail <patola at gmail.com> -
MakerLinux <patola at makerlinux.com.br> - YOUTUBE
<https://www.youtube.com/user/makerlinux>!
Facebook <https://www.facebook.com/patolinux> - Facebook da MakerLinux
<https://www.facebook.com/makerlinux> - Lattes
<http://buscatextual.cnpq.br/buscatextual/visualizacv.do?id=K4763932Z5>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.winehq.org/pipermail/wine-devel/attachments/20210107/36d323ef/attachment.htm>


More information about the wine-devel mailing list