Skip to content
This repository has been archived by the owner on Nov 19, 2019. It is now read-only.

Conflict with existing WINEPREFIX DXVK setup #12

Open
bobwya opened this issue May 17, 2018 · 3 comments
Open

Conflict with existing WINEPREFIX DXVK setup #12

bobwya opened this issue May 17, 2018 · 3 comments

Comments

@bobwya
Copy link

bobwya commented May 17, 2018

If you install DXVK to a WINEPREFIX.
Then install DXUP to same WINEPREFIX.

You end up with:

./d3d10.dll:          symbolic link to /mnt/robs-rog-laptop/linux_shared/robert/wineprefixes/dxvk_steam_64/drive_c/dxup/dxup-x64/d3d10.dll
./d3d10_original.dll: symbolic link to /mnt/robs-rog-laptop/linux_shared/robert/wineprefixes/dxvk_steam_64/drive_c/dxup/dxup-x64/d3d10_original.dll
./d3d10_1.dll:        symbolic link to /mnt/robs-rog-laptop/linux_shared/robert/wineprefixes/dxvk_steam_64/drive_c/dxup/dxup-x64/d3d10_1.dll
./dxgi.dll:           symbolic link to /mnt/robs-rog-laptop/linux_shared/robert/wineprefixes/dxvk_steam_64/drive_c/dxup/dxup-x64/dxgi.dll
./dxgi_original.dll:  broken symbolic link to /mnt/robs-rog-laptop/linux_shared/robert/wineprefixes/dxvk_steam_64/drive_c/dxup/dxup-x64/dxgi_original.dll
./d3dx10_43.dll:      symbolic link to /mnt/robs-rog-laptop/linux_shared/robert/wineprefixes/dxvk_steam_64/drive_c/dxup/dxup-x64/d3dx10_43.dll
./d3d11.dll:          broken symbolic link to /mnt/robs-rog-laptop/linux_shared/robert/wineprefixes/dxvk_steam_64/drive_c/dxup/dxup-x64/d3d11.dll

A little bit of symbolic link mangling would avoid stepping on the DXVK symbolic links. In fact you should be able to easily move the dxgi.dll link origin, DXVK, creates to be a dxgi_original.dll link origin.

Would a pull request for this be useful?

@misyltoad
Copy link
Owner

Yeah it would as I don't have an install to do that on ATM. Could you also dos2unix the setup script. Cheers

@bobwya
Copy link
Author

bobwya commented May 18, 2018

Probably won't be till Monday now... :-)

The execute permissions issue #7 is probably because zip files don't retain execute permissions. I see AppVeyor is using Powershell to build the binaries... Is it possible to set it to package into a different kind of archive? Perhaps .tar.gz or even .rar should be enough?

@axredneck
Copy link

@bobwya issue #7 is due to incorrect encoding as You already know, not due to permissions. chmod +x doesn't help but dos2unix does.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants