Help building wine

[maarten256]

Hello,

I assume there are many threads on this, but I was hoping there was a really easy solution for my problem.

Because my graphics card is not included in Wine, I wanted to add it. So I got the git clone, updated the code and build wine (following the instructions). After installing it, I found it didn't work, the application that was complaining with the stable version installed from winehq didn't even open.

I toyed around for some time, made sure my build environment had all the dependencies, even built the code using separate 32-bit and 64-bit containers but the result was always the same. I downloaded the source using apt source and built that - thinking maybe that'd do the trick - but even that wouldn't work (even if I did not make any changes to the code).

So - I am missing something in my build environment that exists when the deb packages are created (since the stable install with apt works). But I've no idea how to go about figuring that out.

Can someone point me to a build script that was used to generate the current stable deb packages so I can start figuring out what I'm missing?

Thanks!!

[maarten256]

I sort of addressed my own question. I dug into the logs for the jobs that are run on gitlab.winehq.org and built my change in my own fork of the repository. (For some reason the test pipeline fails but I haven't looked into that yet).

I realized that gitlab uses a debian bookworm image to build, so I created my own build image (using the same basic image) and installed all the dependencies. I used that image to compile wine, and installed it. This time it worked - my target application actually ran in the same way as the stable version.

Notionally that solves my problem, although I am no closer to explaining why building wine on debian does result in a usable version, while building on ubuntu does not.