Installing Winehq packages using homebrew 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). To install from a tarball archive, simply unpack it into any directory. 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. from the Terminal, as the PATH variable is set correctly. You can now directly start wine/winecfg/. By clicking on it, a new Terminal window opens with a short introduction into some important wine commands.
After the installation is finished, you should find an entry 'Wine Staging' or 'Wine Devel' in your Launchpad. It is possible to install the package either for all users (needs administrator privileges), or just for your current user. pkg file, double-click on the package, and the usual macOS installer wizard should open. pkg file is recommended for inexperienced users. pkg files and tarball archives are available at. Gatekeeper must not be set to block unsigned packages.īoth.Please test these packages and report any bugs at. 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). Translations of this page: Français (Translators, please see Discussion page.)
