Launching with a custom build of Wine

Open forum for end-user questions about Wine. Before asking questions, check out the Wiki as a first step.
Forum Rules
Post Reply
tramvayak
Newbie
Newbie
Posts: 2
Joined: Sat Jun 28, 2025 4:45 am

Launching with a custom build of Wine

Post by tramvayak »

Hi, I need to use a downgraded version of Wine for one specific program. I compiled it successfully but I can't figure out how to use it. I believe I need to tell the program to use "/path/to/my/wine" instead of "/usr/bin/wine"

"wine --version" outputs the version of my normal wine installation
"/path/to/my/wine --version" correctly outputs the version of the wine I compiled

I tried the environment variables from "man wine"

Code: Select all

       WINESERVER
              Specifies  the  path  and  name of the wineserver binary. If not
              set, Wine will try to  load  /usr/local/bin/wineserver,  and  if
              this  doesn't  exist  it  will then look for a file named "wine‐
              server" in the path and in a few other likely locations.

       WINELOADER
              Specifies the path and name of the wine binary to use to  launch
              new  Windows  processes.  If  not  set,  Wine  will  try to load
              /usr/local/bin/wine, and if this doesn't exist it will then look
              for  a  file  named "wine" in the path and in a few other likely
              locations.
"export WINELOADER=/path/to/my/wine WINESERVER=/path/to/my/wineserver"
checked with "env" that the variables are correct
but "wine --version" still returns the normal installation
the same if I put it all on one line like "WINELOADER=/path/to/my/wine WINESERVER=/path/to/my/wineserver wine --version"

How can I get the command "wine" to point to my binaries? :(
Or is this the wrong way to do it? The program itself isn't a Windows binary, it's a Linux app that uses wine for other things, so I can't just run it with "/path/to/my/wine program"
Thanks
tramvayak
Newbie
Newbie
Posts: 2
Joined: Sat Jun 28, 2025 4:45 am

Re: Launching with a custom build of Wine

Post by tramvayak »

OK, after more testing it actually is using the correct Wine binary when I run the app, but "wine --version" and "which wine" default to /usr/bin/wine? I'm not sure how that works but looks like my problem is solved
User avatar
KenSharp
Level 4
Level 4
Posts: 161
Joined: Mon Jul 13, 2009 8:52 pm

Re: Launching with a custom build of Wine

Post by KenSharp »

"/path/to/my/wine --version" correctly outputs the version of the wine I compiled
You've already done it. You don't need to set anything else. Wine knows where to look for its own binaries.
Post Reply