LinuxQuestions.org - More than one version of Wine?

- Linux - Software (https://www.linuxquestions.org/questions/linux-software-2/)

- - More than one version of Wine? (https://www.linuxquestions.org/questions/linux-software-2/more-than-one-version-of-wine-579993/)

More than one version of Wine?

Is it possible to have 2 versions of Wine on one computer that will not interfere with each other? I have an older version of Wine installed now (0.9.12) and have it set up for an app I love but I don't want to mess with it because it is a pain to fix any problems. I want to leave that one as is. I was hoping that I could have a newer version installed somewhere on this computer that would not cause any compatibility issues. Does anyone know if that is do-able? Has anyone (who knows what they're doing) ever tried it?

Maybe try compiling your own version from source in a seperate directory and then run it from within that directory. It should work.That is the safest way to not let it mix with other system files by chance. You would have to state in the ./configure stage where you would like to compile to and where the libraries should be found. Use configure --help for the options, they are generally well explained.

good luck

This was the result of my compile attempt to my home directory using ./configure prefix=<my home dir/folder where I want Wine>:

configure: lib(n)curses development files not found.
Wine will be built without (n)curses support. (wineconsole.exe)

configure: libicu development files not found.
Wine will be built without bidi (Right to Left) support. (gdi32.dll)

configure: libldap (OpenLDAP) development files not found.
Wine will be built without LDAP support. (wldap32.dll)

configure: WARNING: FontForge is missing.
Fonts will not be built. Dialog text may be invisible or unaligned.

So, I'm not sure if these are needed by the programs I want to try out (ArtRage, Corel Painter Classic, OpenCanvas 1.1 and even WatchTower Library).

I was pretty sure that I had (n)curses since I've compiled a few apps before this so I don't get it...?

bidi im not sure what it is, ldap i dont see why that is needed. ncurses... probably not a prob. make sure that the library is in the lib folder or if not that you specify the path to libs in the config. although before doing that just go to that bin directory and run "./wine" and see if it executes at least

Well I installed it and after I ran the winecfg from within the new directory (which is in a sub folder in my home directory), the already established program, WTLibray crashed. So I deleted the .wine folder (which is in my home directory) and then copied over my backed up files from the old Wine installation.

The Older Wine is still there (in /usr/bin) but the WTLibrary program might be using the newer one, I don't know.

So anyway, I'm confused about the .wine folder -- should there be only one and if there can be two, where should the other one be put so that the new wine will read from that one and not the older one?

It may very well be the .wine which is posing the problem. Either that or the way the wine environment was set up. I am not quite sure what exactly the problem may be... I haven't really tried using wine all that much yet. I am sorry to say that I don't have more advice other than maybe trying to find a way to isolate the new wine to restrict itself to the new folder. Hopefully someone with more knowledge than me would be able to help you out soon.

Quote:

Originally Posted by gymnart (Post 2872448)

Wineproject has a list of packages to install when compiling for various distros here: http://wiki.winehq.org/Recommended_Packages

Note that I have all the packages they recommend for Fedora, but I still don't get bidi support (I double-checked for libicu, too). Still, compiled wine works fine for me, and I've been using it for a while since it's been forever since the Fedora folks updated the wine version in their packages.

Now I don't remember what devel package I got but I had solved the problem with that.

I now found Wine 0.9.42 that will run the two apps I wanted.

Meantime, I did learn a few things from the wine list over at google:
http://groups.google.com/group/comp....e3a8192626ab8a

I also plan to study up on the wineprefixcreate script and make use of these:
export PATH=/some/dir/bin:$PATH
export LD_LIBRARY_PATH=/some/dir/lib:$LD_LIBRARY_PATH

and I was given a script to use:

Code:

-- cut here -------------------------------------------------------------------

#!/bin/sh



export PATH=/dir/for/wine-0.9.44/bin:$PATH

export LD_LIBRARY_PATH=/dir/for/wine-0.9.44/lib:$LD_LIBRARY_PATH



wine $*

-- cut here -------------------------------------------------------------------



Save these lines in a file (e.g. start-wine-0.9.44), make this script

executable:



$ chmod +x start-wine-0.9.44



then test it:



$ ./start-wine-0.9.44 --version

I do remember seeing that when I started up Wine for the first time, it did use the wineprefixcreate script.