Wine: Difference between revisions

From wikinotes
No edit summary
No edit summary
 
(6 intermediate revisions by the same user not shown)
Line 1: Line 1:
wine is a program that converts win32 executables into programs that can run
wine lets you run win32 executables on linux.<br>
natively on *nix systems. This is very awesome, and enables you to use software
[[playonlinux]] is a graphical frontend for it that also manages your wine prefixes.
that would otherwise be unavailable to you (such as MS office, games, etc).
 
As a user-friendly alternative to managing wine directly (managing multiple wine versions, prefixes etc)
a program called [[playonlinux]] was created to wrap around it. It is very convenient.


= Documentation =
= Documentation =
Line 15: Line 11:
</blockquote><!-- Documentation -->
</blockquote><!-- Documentation -->


= Install =
= Notes =
<blockquote>
<blockquote>
 
{| class="wikitable"
== Archlinux ==
|-
<blockquote>
| [[wine install]]
Installing wine from the repo
|-
<syntaxhighlight lang="bash">
| [[wine usage]]
packer -S wine
|-
cower -d lib32-libwbclient
| [[wine configuration]]
</syntaxhighlight>
|-
 
|}
Compiling the most recent version of wine.
</blockquote><!-- Notes -->
<syntaxhighlight lang="bash">
pacman -S gcc-multilib
 
mkdir ~/.wine
git clone git://source.winehq.org/git/wine.git wine-git
configure
make
make depends
make install
</syntaxhighlight>
 
{{ WARNING |
WoW64 support in wine is still being ironed out. Stick with
separate 32 and 64 bit prefixes.
}}
 
 
</blockquote><!-- Archlinux -->
</blockquote><!-- install -->
 
= Usage =
<blockquote>
 
== Running Commands ==
<blockquote>
<syntaxhighlight lang="bash">
env WINEPREFIX=/home/will/.wine/office    wine    /path/to/office.exe
env WINEPREFIX=/home/will/.wine/office    msiexec /path/to/office.msi
 
env WINEPREFIX=/home/will/.wine/office    wineconsole cmd  # opens cmd.exe, then run your .bat or .cmd scripts
</syntaxhighlight>
 
</blockquote><!-- Running Commands -->
 
== Cross Compilation ==
<blockquote>
Firstly, use mingw if you can. It is supported much more natively than msvc under linux.
 
See https://hackernoon.com/a-c-hello-world-and-a-glass-of-wine-oh-my-263434c0b8ad
</blockquote><!-- cross compilation -->
</blockquote><!-- Usage -->
 
= Configuration =
<blockquote>
 
== Prefixes ==
<blockquote>
Wine allows you to create separate ''containers'' for wine installations.
(each representing a different windows system). Each one of these containers
is called a wine '''prefix'''. You are encouraged to create a separate wine
prefix for each program.
 
<syntaxhighlight lang="bash">
## Creating a wine prefix
##
## do not create the directories you want for your wine setup, let winecfg do that for you.
WINEARCH=win64 WINEPREFIX=/home/will/.wine/x64 winecfg
WINEARCH=win32 WINEPREFIX=/home/will/.wine/x86 winecfg
 
## Running Wine Programs with a particular Wine Prefix
export WINEPREFIX="<path to a writable folder on your home directory>"
export WINEARCH="win32"
wine /path/to/office_cd/setup.exe
 
</syntaxhighlight>
 
</blockquote><!-- Prefixes -->
 
</blockquote><!-- configuration -->


= Tools =
= Tools =

Latest revision as of 20:35, 13 March 2022

wine lets you run win32 executables on linux.
playonlinux is a graphical frontend for it that also manages your wine prefixes.

Documentation

official docs: performance https://wiki.winehq.org/Performance

Notes

wine install
wine usage
wine configuration

Tools

winetricks
wine mono

Examples

wine microsoft office
wine zbrush 4r4
wine photoshop CS6