LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Software (http://www.linuxquestions.org/questions/linux-software-2/)
-   -   2 Wine versions and .wine folder conflict (http://www.linuxquestions.org/questions/linux-software-2/2-wine-versions-and-wine-folder-conflict-793434/)

gymnart 03-05-2010 11:22 AM

2 Wine versions and .wine folder conflict
 
Right now, I have wine 0.9.42 installed and it works great with the programs that I have installed.
The thing is, I need to update it but I need to keep the older wine around and able to run for at lest two particular programs (the art programs called, openCanvas 1.1, and ArtRage 1 and 2.)

In the past, I have tried to have 2 versions of wine (0.9.12 and 0.9.42) and I tried following the instructions given me in wine's forums on google groups: I had compiled it to install into its own folder, I had exported the library paths, I had even made a specific .wine042 folder for it to use when I needed to run winecfg to configure that particular version. But no matter what I did, both versions wanted to take over/use the the same .wine folder.

I've also read that you can run wine without having installed it? Really? How is that done? How would you install a program into that wine when it has not been installed so as to test it out? It would be great if I could do that to test if it is compatible with the programs I want to run.

David the H. 03-07-2010 03:06 AM

I've never tried running two different versions at once, so there are no details here, but as I understand it, the secret is to first launch separate wineservers, each configured with it's own wineprefix. Then you direct each program you launch to connect to the appropriate wineserver. It all comes down to the commands you use to launch everything with.

H_TeXMeX_H 03-07-2010 04:32 AM

Use a new WINEPREFIX. Set it to a new directory before running wine:

Code:

WINEPREFIX=$HOME/.wine042 wine game.exe

gymnart 03-07-2010 09:47 AM

So, if I understand it, I can install a new wine in it's own folder (for 1.1.36) (./configure --prefix=/home/<username>/Wine1.1.36), then do I: make depend; make; make install or should I leave out the "make depend"?
Then I should use the WINEPREFIX command to install the desired program as you said, right? If I wanted to run winecfg for the newer version, would I have to use the WINEPREFIX command too?

H_TeXMeX_H 03-07-2010 12:36 PM

You can install wine wherever you want as long as it doesn't overwrite the other wine, and you know which one is which.

wine defaults to 'WINEPREFIX=~/.wine' but if you want a different one so that there isn't a conflict you have to run it as I mentioned above. You can have one wine use the default and the other use another.

gymnart 03-08-2010 09:45 AM

Good! That's exactly what I want.

I still have some questions though:

I'm still wondering if make depend is needed. I didn't use it last time I installed it so could not using it cause problems?

Regarding the .wine file for the newer WINE, could it be in the /home/<username>/Wine1.1.36 folder and have the same name or should it be named something else? Will it insist on being in /home/<username>?

Now, has wine's dependences changed a lot since 0.9.42, as in requiring much newer versions? I'm running an older SuSE kernel so I can't get the newest dependencies even if I wanted to.

H_TeXMeX_H 03-08-2010 11:47 AM

You should run 'make depend' if you plan on running 'make -j#'.

The .wine folder will always be in your home directory, unless you define a WINEPREFIX, you can do that with both versions if you want.

I don't think the dependencies have changed much, you can try it and see.

gymnart 03-09-2010 02:35 PM

I need to make sure I understand the steps right:

./configure --prefix=/home/<username>/Wine1.1.36
make
make install
wineprefixcreate --prefix /home/<username>/Wine1.1.36

Then to install my program:
WINEPREFIX "/home/<username>/Wine1.1.36/.wine" wine program.exe

Let me know if I got it or not.

P.S. Does it matter whether the word(s) wineprefix and wineprefixcreate are in all caps or not?

H_TeXMeX_H 03-10-2010 10:33 AM

[QUOTE=gymnart;3891972]
./configure --prefix=/home/<username>/Wine1.1.36
[quote]

This will install wine in your home folder, is this what you want ? You will have to run wine from here because unless you add it to the $PATH it will not be seen. The executable would probably be at /home/<username>/Wine1.1.36/bin/wine so you would need to run that every time.

Quote:

wineprefixcreate --prefix /home/<username>/Wine1.1.36
This will create a wine prefix in the same directory where wine is installed and will then install window$ programs in there.

Quote:

Then to install my program:
WINEPREFIX "/home/<username>/Wine1.1.36/.wine" wine program.exe
Not quite, try:
Code:

WINEPREFIX="/home/<username>/Wine1.1.36/.wine" /home/<username>/Wine1.1.36/bin/wine game.exe
If you added wine to your PATH, then you'd just use wine instead of the whole path.

Quote:

P.S. Does it matter whether the word(s) wineprefix and wineprefixcreate are in all caps or not?
Linux is case sensitive, so in both cases and all other cases, YES.

gymnart 03-10-2010 11:20 AM

Thanks for clearing that up, that's what I needed.

I'm not quite sure about your statements,
Quote:

"If you added wine to your PATH, then you'd just use wine instead of the whole path."
and
Quote:

"unless you add it to the $PATH it will not be seen."
I thought I had put wine in my PATH for executing the program. Is $PATH where the system wants to look for it?
Does that mean I would have to export library paths each time I wanted to run the new wine or something? That's where I got totally confused the first time I had tried this (and thus failed in my attempt back in about 2007).

Thank you so much for being patient with me!

H_TeXMeX_H 03-10-2010 12:02 PM

I've never actually done an install of wine in my home directory and I don't know if it will require library paths to find the libs it uses, hopefully not.

The PATH is where bash looks for executables, and it will be something like:

Code:

bash-3.1$ echo $PATH
/usr/local/bin:/usr/bin:/bin:/usr/games:/home/demonslayer/bin:/usr/lib64/java/bin:/usr/lib64/qt/bin:/usr/share/texmf/bin:.

It is set automatically by some script somewhere during startup. If wine is not located in one of these directories, you'll have to specify the full path. But, remember that if you run two versions of wine, you can't have both versions called 'wine' in your PATH, so I would first try running it with the full path to be safe.

gymnart 03-11-2010 07:38 AM

Running it with the full path seems easier anyway. I kinda thought that you couldn't have 2 different wines in your path.
I am going to try this when I get more time (gotta get the kid from school early today and tomorrow and then referee him and his sister [from fighting] during the weekend.)

If there's problems, I'll be sure to post here again, and if I'm successful, I'll let ya know that too.


All times are GMT -5. The time now is 05:08 PM.