Translations of this page:Français (Translators, please see Discussion page.)
Unofficial Wineskin and all of its components are 64Bit bar WSGamma due to the lack of source. Wineskin Engines are Wine, meaning if Wine doesn’t work on on macOS Catalina, only CrossOver19 when launched will function on macOS Catalina and I don’t plan on building that on day one. A native install of Linux on your Mac if the district fully support the hardware could mostly work but the CPU turning used within macOS isn’t available for any other OS ran on Mac hardware. Now for running a VM of Linux to then run wine to run a Windows application makes little sense and will end up being much slower then directly running. Third party versions of Wine, such as Wineskin, Winebottler, and PlayOnMac, are not supported by WineHQ. If you are using one of those products, please retest in plain Wine before filing bugs, submitting AppDB test reports, or asking for help on the forum or in IRC. MacOS FAQ; macOS/Building. This is a quick guide to getting Among Us running on macOS. Comment down below if you run into issues. This was tested on macOS Catalina v10.15.5; I can't guarantee compatibility with any other versions.
Wineskin Mac Os High Sierra
Installing WineHQ packages
Official WineHQ packages of the development and stable branches are available for macOS 10.8 to 10.14 (Wine won't work on macOS Catalina 10.15). Please test these packages and report any bugs at http://bugs.winehq.org.
Prerequisites:
- XQuartz >= 2.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 package, and the usual macOS installer wizard should open. The process should be self-explanatory. It is possible to install the package either for all users (needs administrator privileges), or just for your current user. After the installation is finished, you should find an entry 'Wine Staging' or 'Wine Devel' in your Launchpad. By clicking on it, a new Terminal window opens with a short introduction into some important wine commands. You can now directly start wine/winecfg/... from the Terminal, as the PATH variable is set correctly. For user convenience, the package also associates itself with all *.exe files, which means you can run windows executables just by double-clicking on them.
To install from a tarball archive, simply unpack it into any directory. There is no need to set DYLD_* environment variables; all paths are relative, so it should work as long as the directory structure is preserved (you can skip the /usr prefix though using --strip-components 1).
For more information, see https://www.winehq.org/pipermail/wine-devel/2015-December/110990.html and https://www.winehq.org/pipermail/wine-devel/2016-January/111010.html.
Installing Winehq packages using homebrew
Winehq packages can be installed using homebrew
XQuartz can be installed using;
To install wine the following command can be used;
wine-stable, wine-devel or wine-staging packages can be installed using the above example.The advantage of installing via homebrew means wine is available from a standard terminal sessionThe --no-quarantine line to used to above brew adding the quarantine bit
Building Wine
See Building Wine on macOS
Uninstalling Wine
- Remove the source tree and binaries.
Using Homebrew:
Using MacPorts, uninstall the wine package you previously installed:
Wineskin Macos 11
Replace wine with wine-devel if you installed the development version.
Otherwise and if you used `sudo make install`, revert it:
Then simply delete your local Wine source code directory:
- Clean-up pseudo C: drive and registry entries as well as all programs installed to C:
- Check the hidden directory `$HOME/.local/` where Wine stores some desktop menu entries and icon files as it interoperates with the X.Org Foundation and the Free Desktop.
Note: Files in this directory are unused on macOS unless you use a UNIX window manager and other X11 applications instead of the native MacOS apps.
Third Party Versions
Third party versions of Wine, such as Wineskin, Winebottler, and PlayOnMac, are not supported by WineHQ. If you are using one of those products, please retest in plain Wine before filing bugs, submitting AppDB test reports, or asking for help on the forum or in IRC.