[Bug 44775] [winevulkan] Failed to open dynamic library

[wine-bugs at winehq.org]

https://bugs.winehq.org/show_bug.cgi?id=44775

--- Comment #11 from Trent McP <twilightinzero at gmail.com> ---
(In reply to GG from comment #10)
> Any advice to get a "compiled" version of wine 3.4 x64 or I have to install
> all libs/headers and compile myself ?
> Any issue if I use an LXC to compile instead of my master system ?

I actually have tried multiple pre-built versions: 3.4, staging-3.4, and
vulkan-3.3 all from the Lutris repo (I don't use Lutris itself, just its
builds), as well as the WineHQ PPA. What's your distro? Even if you're not
Debian/Ubuntu, you can just pull the wine-devel folder out of the .deb file and
throw it somewhere since it just installs it in /opt.

That said, I think it hard to believe that every single one of these pre-built
versions--even the official PPA--would exclude vulkan support. I don't know if
Lutris makes build logs available. Which file would I ldd to see if it tries to
load Vulkan?

(In reply to Roderick from comment #8)
> A log is useful. Optimus kind of setups I'm a bit worried about, as Optimus
> is a set awful hacks. We are probably not ready for that.

I'm glad to hear from the man himself! Okay, so on my setup personally, when I
start up my Prime X, I automatically set VK_ICD_FILENAMES to the location of
nvidia_icd.json on my system. Dolphin's Vulkan backend works with this and
gives me great performance. I don't do anything with that env var when I want
to use Intel.

I'll get the logs for the Intel run and also make you logs for the Prime X run,
but I feel like they were mostly identical.

-- 
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.