Download Winebottler for Mac Os X 10.8 Updated

Download Winebottler for Mac Os X 10.8

Translations of this page: Français (Translators, please meet Discussion page.)

Installing Depreciated WineHQ packages

Official WineHQ packages of the development and stable branches are available for macOS x.eight to 10.14 (Wine won't work on macOS Catalina 10.15) . Please exam these packages and report any bugs at http://bugs.winehq.org.

Prerequisites:

XQuartz >= ii.7.7
Gatekeeper must not be set to block unsigned packages.

Installing:

Both .pkg files and tarball archives are available at https://dl.winehq.org/wine-builds/macosx/download.html.

Installing from a .pkg file is recommended for inexperienced users.

To install from a .pkg file, double-click on the packet, and the usual macOS installer wizard should open. The process should be cocky-explanatory. It is possible to install the parcel either for all users (needs administrator privileges), or but for your current user. Later the installation is finished, you lot should notice an entry "Wine Staging" or "Vino Devel" in your Launchpad. By clicking on information technology, a new Terminal window opens with a short introduction into some of import wine commands. You lot can now directly outset vino/winecfg/... from the Concluding, as the PATH variable is set correctly. For user convenience, the bundle too assembly itself with all *.exe files, which ways you tin can run windows executables just past double-clicking on them.

To install from a tarball archive, simply unpack information technology into any directory. There is no need to ready DYLD_* surroundings variables; all paths are relative, and then information technology should work as long equally the directory structure is preserved (y'all can skip the /usr prefix though using --strip-components 1).

For more data, see https://www.winehq.org/pipermail/wine-devel/2015-December/110990.html and https://world wide web.winehq.org/pipermail/wine-devel/2016-January/111010.html.

Installing Wine packages using homebrew

Winehq packages can exist installed using homebrew

To install wine the following command tin can be used;

brew tap homebrew/cask-versions brew install --cask --no-quarantine (selected wine package)

vino-stable, vino-devel or vino-staging packages can be installed using the above example. The advantage of installing via homebrew means wine is available from a standard terminal session The --no-quarantine line is to avert mash adding the quarantine flag.

Building Wine

See Building Wine on macOS

Uninstalling Wine

Remove the source tree and binaries.

Using Homebrew:

brew uninstall --cask (selected wine packet)

Using MacPorts, uninstall the wine package yous previously installed:

sudo port uninstall --follow-dependencies wine

Supervene upon vino with vino-devel if you installed the development version.

Otherwise and if yous used `sudo make install`, revert it:

sudo make uninstall

So simply delete your local Wine source code directory:

rm -rf src/wine

Clean-upward pseudo C: drive and registry entries as well equally all programs installed to C:

rm -rf $HOME/.wine

Cheque the hidden directory `$Habitation/.local/` where Wine stores some desktop bill of fare entries and icon files as it interoperates with the X.Org Foundation and the Free Desktop.

rm -rf $HOME/.local

Notation: Files in this directory are unused on macOS unless you use a UNIX window director and other X11 applications instead of the native MacOS apps.

Tertiary Party Versions

3rd party versions of Wine, such every bit Wineskin, Winebottler, and PlayOnMac, are non supported by WineHQ. If you are using one of those products, please retest in plain Wine earlier filing bugs, submitting AppDB test reports, or asking for assist on the forum or in IRC.