id like to have a single wine install wich uses another folder then ~/.wine. so i want it not to share this folder with my common wine installation. any ideas? thx looki
2008/5/12 looki <wineforum-user at winehq.org>:> id like to have a single wine install wich uses another folder then ~/.wine. > so i want it not to share this folder with my common wine installation. > any ideas?You can use any number of different Wine fake-windows folders (.wine or whatever). In fact, it's a good way to get tricky applications to work. Note that you need to fiddle with the command line a bit. Doing this will set up a separate fake-Windows called .wine2 : export WINEPREFIX=~/.wine2 wineprefixcreate You need to make sure your apps inside .wine2 are started with $WINEPREFIX set to .wine2 . (An automated version of this is how Crossover does "wine bottles" to keep apps separated.) You don't need to do this normally - but when a particular app needs fiddly settings, or Wine pretending to be a different version of Windows or something, it's very useful. - d.
ok thx. assuming i have different wine installations (made with ./configure --prefix=folder_version) and i now use for every wine version WINEPREFIX=folder_version wine_version anyprogram. do i have any intersections between the different wine installations? my intension is to wrap a whole wine installation by a program (with a gui), so that my program and its own wine, doesnt touch the users own wine installation. greetz looki
ok thats what i try to get :) one question, when i do "make instal", wine goes to a directory. is this directory important? i mean can i prefix it to opt/wine60 and after this copying the whole content to /home/wine, without trouble using it in another folder? so that another guy can simply unpack it in his own folder and use it? my program would just use the relative path to get wine, but will wine do the same? greetz looki
looki wrote:> ok thx. > assuming i have different wine installations (made with ./configure --prefix=folder_version) and i now use for every wine version > WINEPREFIX=folder_version wine_version anyprogram. >Wrong. WINEPREFIX points to ~/.wine directory - Wine's "configuration". Wine is not installed there. The directory you give to configure with "--prefix" is the directory Wine will be installed into on 'make install'. To use _that_ Wine installation you need to specify full path when running it. Example Code: ./configure --prefix=/opt/wine_special make depend all install WINEPREFIX=$HOME/special_program /opt/wine_special/bin/wine special_program.exe
the program would do it like this WINEPREFIX=./windows ./wine/bin/wine ./folder/aprogram.exe and i only dont know, if this leads to problems with wine, because the . folder might differ for every user.
On Mon, May 12, 2008 at 2:17 PM, looki <wineforum-user at winehq.org> wrote:> one question, when i do "make instal", wine goes to a directory. is this directory important? > i mean can i prefix it to opt/wine60 and after this copying the whole content to /home/wine, without trouble using it in another folder?IMHO you should use --prefix=/opt/yourappname/wine and never change it. Or are you trying to let users copy the app into their home directory and run it from there?
yes its ment to be very simple. just unpack the files and execute my program and enjoy. my program then runs another self written windows program which can do some convenience stuff with a windows game, like running it with long command line arguments just by a click on a button. the whole pack must include a patched wine0.9.44 due to regression issues with wine. and it would be good if a user of my prog dont need to care about its own wine installation and folders and things.
On Mon, May 12, 2008 at 4:29 PM, looki <wineforum-user at winehq.org> wrote:> yes its ment to be very simple. > just unpack the files and execute my program and enjoy.Then definitely look at how Navicat does it.> the whole pack must include a patched wine0.9.44 due to regression issues with wine.Have you reported the bugs?
> the whole pack must include a patched wine0.9.44 due to regression issues with wine. >Have you reported the bugs?[/quote] its about this game: http://appdb.winehq.org/objectManager.php?sClass=version&iId=1744
On Mon, May 12, 2008 at 4:40 PM, looki <wineforum-user at winehq.org> wrote:> its about this game: > http://appdb.winehq.org/objectManager.php?sClass=version&iId=1744You might not need to put together your custom wine, then. I think the bug is http://bugs.winehq.org/show_bug.cgi?id=11814 which is a dup of a bug targeted for 1.0. Cross your fingers...
wine 1.0rc1 doesnt get it, i tried it today. but anyway the idea to this prog came to me, because there is a programm needed for playing replay files and doing other stuff with them. as i know this only possible with command line arguments. and they are long. on windows u get it over a context menue that opens by right clicking the replay file. of course my vision is not really needed and i could only write a simple windows prog that opens the replay files. but i wanted to give this a try, because it makes sence to seperate one wine installation just for this game and then of course giving it to all :)