How to use the wineprefix with another wine-path

[abb4]

Hi, there
I recently purchased a copy of bordeaux in order to try the dib engine (and pulse) in wine1.2
I would like to use this in already installed bottles.

So I tried something like this:

code: [export WINEDIB=ON]
then (as an example)
code:[/opt/bordeaux/bin/wine | env WINEPREFIX=~/.wine-test wine winecfg]

This does create a wine bottle, but in this way the dib engine doesn't get loaded in the program I use.

Any ideas how to do this in a proper way?

[abb4]

Nobody?


It works with the default wine bottle
code:
[/opt/bordeaux/bin/wine 'C:\Program Files\winamp\winamp.exe']

This also works
code:
[env WINEPREFIX=~/.wine-winamp wine 'C:\Program Files\winamp\winamp.exe']

How do I combine them in one command?

[Gert van den Berg]

On Sun, Aug 15, 2010 at 17:35, abb4 <[email protected]> wrote:

Nobody? [Crying or Very sad]

You won't get help with Bordeaux here, ask their forum...

[James McKenzie]

abb4 wrote:

Nobody? [Crying or Very sad]


It works with the default wine bottle
code:
[/opt/bordeaux/bin/wine 'C:\Program Files\winamp\winamp.exe']

This also works
code:
[env WINEPREFIX=~/.wine-winamp wine 'C:\Program Files\winamp\winamp.exe']

How do I combine them in one command?

This looks like a generic Wine question, as Wine 'bottles' can be put
anywhere....

You can call the wine program from anywhere (the default prefix is /usr
but you can set it to be /somewhere/on/mars if you wish.)

Command line:

env WINEPREFIX=$HOME/.wine-amp; cd $HOME/.wine-amp/drive_c/Program\
Files/winamp; /opt/bordeaux/bin/wine winamp.exe

Does it all on one line. The semi-colons separate individual commands
(a book on shell programming is a good thing to own.)

James McKenzie

[abb4]

What does it matter if one builds there own Wine or buys one,
same issue applies (if you would like to install this separately from the main Wine), it's all Wine..

Anyway I kind of figured it out. (no thanks)

code:
[env WINEPREFIX="/home/username/.wine-winamp" /opt/bordeaux/bin/wine "C:\Program Files\winamp\winamp.exe"]

[abb4]

To James McKenzie

Programming has never been my strongest..(hence the questions)
Thanks for the reply, I can now try and play a bit more around.

[abb4]

Hehe, I've got a working dib engine
Even AlbumPlayer works..

Thank's again.

[Gert van den Berg]

On Sun, Aug 15, 2010 at 18:21, abb4 <[email protected]> wrote:

What does it matter if one builds there own Wine or buys one,
same issue applies (if you would like to install this separately from the main Wine), it's all Wine..

I thought the prefixes worked (and assumed the user knows how
environment variables worked...) but that the DIB engine was not
working in the prefix...

Gert

[abb4]

On Sun, Aug 15, 2010 at 18:21, abb4 <[email protected]> wrote:

What does it matter if one builds there own Wine or buys one,
same issue applies (if you would like to install this separately from the main Wine), it's all Wine..

I thought the prefixes worked (and assumed the user knows how
environment variables worked...) but that the DIB engine was not
working in the prefix...

Gert

It does work here
code:
[env WINEPREFIX=$HOME/.wine-ap52; cd $HOME/.wine-ap52/drive_c/'Program Files'/AlbumPlayer; /opt/bordeaux/bin/wine AlbumPlayer.exe]

[James McKenzie]

abb4 wrote:

Gert van den Berg wrote:

On Sun, Aug 15, 2010 at 18:21, abb4 <[email protected]> wrote:

What does it matter if one builds there own Wine or buys one,
same issue applies (if you would like to install this separately from the main Wine), it's all Wine..

I thought the prefixes worked (and assumed the user knows how
environment variables worked...) but that the DIB engine was not
working in the prefix...

Gert

It does work here
code:
[env WINEPREFIX=$HOME/.wine-ap52; cd $HOME/.wine-ap52/drive_c/'Program Files'/AlbumPlayer; /opt/bordeaux/bin/wine AlbumPlayer.exe]

The question I have is which DIB engine? The one for Wine has
repeatedly been shot down by Alexandre Julliard. The last person to
touch it gave up after much work was done, but a lot more work is needed
before the entire product can go into production.

If the Bordeaux project has one, why doesn't Wine?

James McKenzie

[Gert van den Berg]

On Sun, Aug 15, 2010 at 22:06, James McKenzie wrote:

The question I have is which DIB engine?  The one for Wine has repeatedly
been shot down by Alexandre Julliard.  The last person to touch it gave up
after much work was done, but a lot more work is needed before the entire
product can go into production.

My guess would be Massimo Del Fedele's version...

http://wiki.winehq.org/DIBEngine has a lot of info...

If the Bordeaux project has one, why doesn't Wine?

Probably, because even though the code works, it is not maintainable /
structured wrongly?

Gert

[James McKenzie]

Gert van den Berg wrote:

On Sun, Aug 15, 2010 at 22:06, James McKenzie wrote:

The question I have is which DIB engine? The one for Wine has repeatedly
been shot down by Alexandre Julliard. The last person to touch it gave up
after much work was done, but a lot more work is needed before the entire
product can go into production.

My guess would be Massimo Del Fedele's version...

http://wiki.winehq.org/DIBEngine has a lot of info...

Interesting, as this is the version that I witnessed AJ literally 'kill'
while it was in progress. Max was making great progress. However, that
was a wall way to high to climb on the first go round,

If the Bordeaux project has one, why doesn't Wine?

Probably, because even though the code works, it is not maintainable /
structured wrongly?

My intuition says the same thing if it is Max's code. However, if he
cleans it up and gets it somewhat right, he can always try again. There
was much more work to be done, especially for the Mac/Solaris crowd.

James McKenzie

[abb4]

On Sun, Aug 15, 2010 at 18:21, abb4 <[email protected]> wrote:

What does it matter if one builds there own Wine or buys one,
same issue applies (if you would like to install this separately from the main Wine), it's all Wine..

I thought the prefixes worked (and assumed the user knows how
environment variables worked...) but that the DIB engine was not
working in the prefix...

Gert

It does work here
code:
[env WINEPREFIX=$HOME/.wine-ap52; cd $HOME/.wine-ap52/drive_c/'Program Files'/AlbumPlayer; /opt/bordeaux/bin/wine AlbumPlayer.exe]

After all I found the DIB engine doesn't work in the prefix.
I had a version of AlbumPlayer installed in .wine which the DIB part was falling back into
Once I removed .wine the code as above didn't work any more.

[James McKenzie]

abb4 wrote:

abb4 wrote:

Gert van den Berg wrote:

On Sun, Aug 15, 2010 at 18:21, abb4 <[email protected]> wrote:

I thought the prefixes worked (and assumed the user knows how
environment variables worked...) but that the DIB engine was not
working in the prefix...

Gert

It does work here
code:
[env WINEPREFIX=$HOME/.wine-ap52; cd $HOME/.wine-ap52/drive_c/'Program Files'/AlbumPlayer; /opt/bordeaux/bin/wine AlbumPlayer.exe]

After all I found the DIB engine doesn't work in the prefix.

This would have to be copied from the working .wine to the new prefix
and then repointed to work with the new prefix. This is not trivial.

James McKenzie

[abb4]

This would have to be copied from the working .wine to the new prefix
and then repointed to work with the new prefix. This is not trivial.

Doing so a new .wine is created
Are you sure the DIB part can work in the prefix?