Talk:DXVK

Note
Before creating a discussion or leaving a comment, please read about using talk pages. To create a new discussion, click here. Comments on an existing discussion should be signed using ~~~~:

A comment [[User:Larry|Larry]] 13:52, 13 May 2024 (UTC)
: A reply [[User:Sally|Sally]] 12:47, 5 November 2024 (UTC)
:: Your reply ~~~~

Graphic designer inner me needs help

Talk status

This discussion is done.

BT - How do you want to style it? I would just put "=" everywhere.. DXVK#Pre-built_release

--Kreyren (talk) 06:08, 22 September 2018 (UTC)

Upstream dropped winelib support

Talk status

This discussion is still ongoing.

Upstream has removed the ability to build using winelib as of this commit.

Since this page only talks about using winelib to build DXVK. I think it would be a good idea to include instructions on setting up a mingw toolchain via crossdev.

TheGreatMcpain (talk) 18:24, 24 April 2020 (UTC)

I've added instructions for installing Mingw. It may be a bit too short, maybe it needs some more explanation? --Tastytea (talk) 19:48, 24 April 2020 (UTC)

Could you also add "--disable-sjlj-exceptions --with-dwarf2" to EXTRA_ECONF? According to Proton's build-mingw-w64.sh build script it helps with performance on 32bit. Also, in your crossdev command you can add '--libc ">=7.0.0"' to force crossdev to use >=mingw64-runtime-7.0.0 automatically.

--TheGreatMcpain (talk) 03:18, 25 April 2020 (UTC)

Added the exception stuff as a recommendation because DWARF-2 may not always work. I'm not sure what '--libc ">=7.0.0"' does exactly. Will it unmask mingw64-runtime? Can you add it?

--Tastytea (talk) 16:16, 29 April 2020 (UTC)

Basically '--libc ">=7.0.0"' will unmask mingw64-runtime versions 7.0.0 and up. I'll go ahead and add it.

--TheGreatMcpain (talk) 19:08, 6 May 2020 (UTC)

I was experimenting with crossdev yesterday and found out that I could simply run

root #crossdev -S --libc "~7.0.0" -t x86_64-w64-mingw32

root #crossdev -S --libc "~7.0.0" --lenv 'USE="libraries"' --genv 'EXTRA_ECONF="--enable-threads=posix"' --init-target -t x86_64-w64-mingw32

root #emerge -1v cross-x86_64-w64-mingw32/mingw64-runtime

root #emerge -1v cross-x86_64-w64-mingw32/gcc

to get a working toolchain.

I think this is a cleaner way of doing it, because we're letting crossdev handle the configuration files instead of using echo to manually create them.

Plus, by doing it like this the user won't have to delete those files if they need to rebuild their mingw toolchain from scratch.

TheGreatMcpain (talk) 17:41, 25 September 2020 (UTC)

I agree, that's a lot cleaner. Could you change it? --Tastytea (talk) 16:23, 8 October 2020 (UTC)

Do Lutris instructions work?

Talk status

This discussion is still ongoing.

In Lutris, I can only select DXVK yes or no. In ~/.local/share/lutris/runtime/dxvk/ there is the directory 1.7.3L-03f11ba. It would seem that Lutris selects the DXVK version with the highest version number? Does anybody know more? --Tastytea (talk) 13:03, 5 February 2021 (UTC)