Install and run Wine purely in/from the home folder

[ubyx]

Hello folks.

I have a little question for you.

First to the background. I have a windows program (command line based) that is able to run just fine in the wine environment.
Now I want to run it on our linux HPC server (no multi-threading and so on is needed). There is no wine installed by default, and as I'm no admin I can't install it there. So is it possible to make wine run purely out of my home folder? Then I would have an "wine package" that I could simply copy in there and run the program...

Thank's for any help.

[Frédéric Delanoy]

On Tue, Sep 13, 2011 at 09:50, ubyx <[email protected]> wrote:

Hello folks.

I have a little question for you.

First to the background. I have a windows program (command line based) that is able to run just fine in the wine environment.
Now I want to run it on our linux HPC server (no multi-threading and so on is needed). There is no wine installed by default, and as I'm no admin I can't install it there. So is it possible to make wine run purely out of my home folder? Then I would have an "wine package" that I could simply copy in there and run the program...

Thank's for any help.

You can compile wine and run it from any directory.
Just use sthg like /path/to/wine path/to/your/prog.exe

[ubyx]

Ok, thanks.

So have I to compile with the correct prefixes. Somethink like

./configure -prefix=$home/wine_for_me

then I compile and install.
After that I could simply copy the wine folder to my folder on the server?

[Frédéric Delanoy]

On Tue, Sep 13, 2011 at 17:49, ubyx <[email protected]> wrote:

Ok, thanks.

So have I to compile with the correct prefixes. Somethink like

./configure -prefix=$home/wine_for_me

then I compile and install.

You don't even have to specify a prefix if you don't do a make install
(i.e. you just do './configure && make' then run wine by specifying
the full wine path
like '/path/to/compiled/wine yourprog'

After that I could simply copy the wine folder to my folder on the server?

yes but compiling on a system and running on another can be
problematic, e.g. if some libraries are not installed on the
destination machine (or different versions, ...)
You should preferably compile on the destination machine.

[ubyx]

I'll try that.
Thank you very much!

[vitamin]

yes but compiling on a system and running on another can be problematic.

If they are different distros or different versions of the same distro. But not never a problem if it's the same version of the same distro.

[perryh]

Fr??d??ric Delanoy <[email protected]> wrote:

You can compile wine and run it from any directory.

Correct.

Just use sthg like /path/to/wine path/to/your/prog.exe

No, most Windows programs need to be run from their own directories.

$ cd path/to/your
$ /path/to/wine prog.exe

[ubyx]

Fr??d??ric Delanoy <[email protected]> wrote:

You can compile wine and run it from any directory.

Correct.

Just use sthg like /path/to/wine path/to/your/prog.exe

No, most Windows programs need to be run from their own directories.

$ cd path/to/your
$ /path/to/wine prog.exe

Yes, that's need to be done with my program.
Otherwise it will not find some files.

[ubyx]

Another question:
The program has a high i/o frequencyto an access database while calculating.
This makes the program ca. 5 times slower than in a native windows environment.
Is there a dirty little trick to speed this up a little in wine?

Thanks. So far it works nice (despite the speed).

[Martin Gregorie]

On Wed, 2011-09-14 at 15:38 -0500, ubyx wrote:

Another question:
The program has a high i/o frequencyto an access database while calculating.
This makes the program ca. 5 times slower than in a native windows environment.
Is there a dirty little trick to speed this up a little in wine?

If it uses an ODBC driver to talk to Access, there's a good chance you
can replace Access with a native database, e.g. PostgreSQL.


Martin