View Single Post
allnameswereout's Avatar
Posts: 3,397 | Thanked: 1,212 times | Joined on Jul 2008 @ Netherlands
#32
No, WINE for ARM is not useful with an x86-32 emulator. Those who think so are confusing the 2 following situations:

1) ARM/Linux -> WINE for ARM -> Windows/ARM binary (usually means an open source Windows application)
2) ARM/Linux -> x86-32 emulator-> WINE for x86-32 -> Windows/x86-32 binary (almost all (proprietary) Windows applications in existence)

Clearly, we're discussing option 1 which is most useful for portability and debugging reasons. Option 2 means you must emulate a wholex 86-32 architecture which is too much a performance impact to even consider. Option 2 also has another disadvantage that all Windows applications are written for a Windows desktop UI with mouse and keyboard instead of for a device with the UI experience as Nokia N900 with Maemo 5.

If you really have to use Windows applications there are more suitable solutions such as running it on a x86-32 portable computer (netbook or w/e), or something smaller w/o a screen, or a server you connect to from your N900 using e.g. rdesktop.

@ mail_e36 yes you can set your WINE homedir to something else. E.g. WINEPREFIX=/tmp/temporary_wine /usr/bin/wine /root/notepad.exe

This is explained in the manual:

WINEPREFIX
If set, the content of this variable is taken as the name of the directory where wine stores its data (the default is $HOME/.wine ). This
directory is also used to identify the socket which is used to communicate with the wineserver. All wine processes using the same wine‐
server (i.e.: same user) share certain things like registry, shared memory, and config file. By setting WINEPREFIX to different values for
different wine processes, it is possible to run a number of truly independent wine processes.
__________________
Goosfraba! All text written by allnameswereout is public domain unless stated otherwise. Thank you for sharing your output!