Winehq For Mac Os



Catalina compatible CrossOver Mac 19 is the easiest way to run Microsoft Windows software on your Mac without buying a Windows license, rebooting or using a virtual machine. CrossOver Mac makes it easy to launch Windows programs natively from the dock, and integrates macOS functionality like cross-platform copy & paste and shared file systems. According to a post by a moderator on forum.winehq.org, the CodeWeavers solution likely won't be merged into the official Wine. I'd take what they say with a grain of salt though because the things they say about ELF vs PE (or Mach-O vs PE in the case of macOS) don't really seem directly applicable to the issue at hand. Run Windows programs seamlessly on your Mac. Wine, which stands for Wine Is Not an Emulator, takes a different approach: since macOS is POSIX compliant, Wine translates the Windows API calls into POSIX calls in order to be understood by Apple’s operating system. The conversion is done on-the-fly and enables you to integrate Windows. See full list on wiki.winehq.org.


Translations of this page: not yet ported. Translators see Discussion page.

See also the general Wine FAQ

  • 12How to create shortcut, launcher, or .app to start a given .exe?

1 What is the difference between Wine and Darwine?

Darwine was the original effort to port Wine to Macs Running macOS and consisted of 2 major efforts.

  1. PowerPC Macs - attempted to integrate QEMU into Wine for x86 CPU emulation
  2. Intel x86

Wine for macOS x86 has now merged into main Wine project, here at WineHQ. Darwine is no longer actively developed.

2 What does Wine on macOS support? (DirectX, DirectSound, Direct3D...)

  • Sound should be working just fine since Wine release 0.9.15.
  • MIDI output (via Apple's built-in software synthesizer) works.
  • 3D (OpenGL Support) works. Note that due to Apple's X11 often being outdated, we recommend you install XQuartz, available since 10.5 Leopard, which closely follows Xorg development. Since macOS 10.5.7, Apple X11 may be good and recent enough for wine 3D usage.
  • Full screen mode works in a Wine release as old as 1.1.24. However, there are too many restrictions to make it generally useful:
  • Unlike CodeWeaver's X server packaged with their CrossOverMac product, Apple's X11.app will not change the screen resolution. So your app must support your monitor's likely huge native resolution, e.g. 1600x1200. If your app knows only 800x600 and 1024x768, it will not start and may even crash.
  • Some modern apps, although they may support your monitor's resolution during play, start with logos and intro animations that want to open a screen at 640x480 or 800x600. This will fail and may cause your application not to start at all or even crash. For instance, the game 2weistein - Das Geheimnis des roten Drachen - works well in full screen, yet the screen stays black at start, trying to display the first intro animation, while the subsequent second logo, intro movie and game logo all scale nicely to full screen.
  • The X11 menu bar will remain visible at all times. The app sees a screen resolution 22 pixel less than it really is, e.g. 1600x1178.
  • The dock will stay in front of the fullscreen window. Use its auto-hide feature to get rid of it.
  • 'Always on top' windows remain atop Wine's fullscreen window, e.g. window #3 of the CPU% activity meter -- exactly like they do in !TimeMachine's full screen display. Just close or hide them.
  • Running a Fullscreen program in a Wine Virtual Desktop window should work fine
  • Starting in Xquartz 2.6.0 (available Oct-Nov 2010), RandR and resolution changing should be working on Macs.
  • mcicda.dll does not work (bug #20323), so apps will not play music off CD tracks.
  • Multi-CD installs work, using the `wine eject` command.
  • More generally, CD-ROM support is incomplete, so Wine will not start many copy-protected apps.

3 How do I change settings?

  • If you built a plain wine: run /path/to/your/wine winecfg as on any other UNIX.
  • Audio output will only be enabled after you ran winecfg to configure it.

4 Where are Wine's settings stored?

In your home folder (/Users/<username>/ resp. ~/) in the hidden folder .wine. You can get into (even hidden) folders in the Finder by pressing Shift+Command+G and entering the path, for example ~/.wine.

You can make the hidden folder 'visible' by creating a symbolic link: ln -s ~/.wine wine in Terminal.app.

5 How can I switch the locale?

This Wiki and other Wine documentation mention setting the environment variable LANG. This works for UNIX but deliberately does not work with Wine on MacOS for reasons enumerated in this thread. Instead, set the variable LC_MESSAGES, e.g. use LC_MESSAGES=ja_JP.UTF-8 wine japanese.exe or LC_MESSAGES=ja_JP.SJIS or LC_MESSAGES=fr_FR.UTF-8

6 Will there be a PowerPC version (or will there be a way to run Wine on a PowerPC processor)?

Darwine was the effort to port Wine to PowerPC processors. Darwine is NO LONGER ACTIVELY DEVELOPED.

7 Where can I get a working Wine for Intel Macs?

  1. WineHQ builds packages for macOS 10.8 and higher.
  2. You can compile wine from source with XCode and XQuartz. See macOS/Building for additional troubleshooting and directions.
  3. If you are a Fink or MacPorts user, consider installing the wine or wine-devel package.
  4. you can also check out the Third Party Applications page for info about other Apps that use Wine that may be much easier to use than building Wine yourself. Note that these products are not supported here, so please do not file bugs, submit AppDB test reports, or ask for help on the forum or in IRC if using one.

8 All 16 bit applications crash in winevdm.

This is radar://5935237 bug in Apple's linker, which affects XCode older than 3.2.x. It is reflected in Wine Bug #14920. 32bit apps are not affected. affects

Workarounds:

  • Build wine yourself with win16 support
    • macOS 10.4 Tiger: compile using Xcode 2.x b. macOS 10.5 Leopard: patch Xcode linker bugs, then compile
    • download the ld64 linker patch as described in Bug14920 comment29
    • apply the ld64 linker patch as described in Bug14920 comment38
  • macOS 10.6 Snow Leopard or later: compile using Xcode 3.2.x or later

9 How do I right-click in Wine on macOS?

Control-click, as you're probably used to, won't work in wine (so far?). Workaround: Enable secondary click by tapping the trackpad with two fingers. Therefor go to System Preferences > Keyboard & Mouse > Trackpad and enable 'Tap trackpad using two fingers for secondary click'. You can then do the right clicks by tapping the trackpad with two fingers.Update: if you are running a current version of Xquartz, you can go into the X11.app preferences when it's running and select what you want to be modifier keys for right and middle clicks.

10 How come my keyboard shortcuts don't work like normal

Wine by default maps the keys differently than native macOS applications.It's possible to change some of the keyboard mappings depending on the version of wine being used.

  • Since Wine 1.7.4 its possible to map Option as Alt by adding the following using regedit
  • Since Wine 3.17 it's possible to map Command as Ctrl meaning CMD+C/CMD+V now functions like Native applications
Winehq mac os x

11 How to launch wine from terminal instead of the wine application?

To do this we need to add the wine application to the PATH variable

To do that we do the following

Then copy in the following

Comment out Wine Stable uncomment out the one you want to be added for use within terminal.To save press Ctrl+X then press Enter to save the file.Now any new terminal session will have wine from available the chosen wine application for the current user.

12 How to create shortcut, launcher, or .app to start a given .exe?

12.1 Instructions on making .app file launcher

This is for real Wine, installed to /usr/local. It can be modified to work with Macports Wine.

  • open up Apple's Script Editor
    • in macOS 10.6 to 10.9 this is '/Applications/Utilities/Applescript Editor.app'
    • in macOS 10.4 and 10.5 this is '/Applications/AppleScript/Script Editor.app'
    • in macOS 10.10 and up, this is '/Applications/Utilities/Script Editor.app'
  • Copy and paste the following code into Script Editor:
  • Edit the program per the directions in the lines that start with --
  • if everything is default, you only need to edit the 'set toRun' line
  • After you have edited it for your program, save it as an 'Application' (not a script) in the script editor
  • this will create a .app for you that you can double click to run what you specified.

It might start up a bit slow with no visual indicators... sometimes, be patient

12.2 Instructions on making custom launcher what invokes Terminal
  • Using TextEdit create text file with following contents:
  • The $HOME, in the beginning of the path, will expand to the home directory, in case of user Me, it will expand to /Users/Me
  • The dot(.) in the WINEPREFIX folder will make it invisible, you can omit the dot to leave folder visible and easier to work with
  • By default, wine uses /Users/YourUsername/.wine prefix, you can be creative and use other prefixes and paths to store multiple prefixes
  • If you need to define other constants for wine e.g. export WINEDEBUG=fixme-d3d,warn+heap,+debugstr or export LC_ALL=ru_RU.UTF-8, add all of them before the cd command.
  • If the program is inside the wine prefix, cd might look something like this: cd '$WINEPREFIX/drive_c/Program Files/theprogram/'
  • In case you want to use custom path to wine, you may replace `wine` on the last line with /path/to/wine/wine
  • Some programs may still have trouble starting, you can try to replace `wine 'myapp.exe'` with wine start /unix '$HOME/where/is/my/app/myapp.exe'

After making all customizations, save the launcher file as regular .txt file.Next, in the Finder, click on saved launcer file, then press Command+I (Get Info) and replace the .txt with .command which is an extension that Mac OS uses for shell (and perl, Python, tcl) scripts.Alternatively, you can remove file extension altogether.

Next, you need to give launcher file executive permissions. Open the Terminal and execute chmod +x path/to/my/something, where path/to/my/something is the path to the launcher file.

  • You can always change the code of the launcher by opening it with the TextEdit again. After adding changes, simply save the launcher file without renaming.

Optional: Changing the icon of the launcher file

On the macOS, it is possible to change the icon of any file to anything you desire.

NOTE: In some cases, your custom icon will not display if launcher file has extension. Refer to previous steps on how to rename the launcher.

Look into the hidden `~/.local/share/icons/` directory, where Wine keeps the icons created by application installers (.xpm and .png files); they would display on a Linux desktop.

In some cases, you will need to manually extract the icon from the .exe file. This can be done using tools like Resource Hacker. This tutorial, however, will not cover the process of doing it. It is assumed, that you have the application icon in the `.ico` or `.png` format.

Now that you have your icon file ready, open it with the Preview. In case of .ico it might have multiple frames/images inside, select appropriate one. Press Command+C (Edit>Copy). Next, in the Finder, click on the launcher file, then press Command+I (Get Info). In the top left corner of the launcher info, there will be a small image showing current icon, click on it to highlight it. Press Command+V to paste your icon.If everything goes well, the icon of your launcher will change.

13 Why is it building font metrics? This may take some time...

Actually, there are two bugs involved:

  1. Bug #17674 'wine recaching font metrics on every run', consuming upto 30 seconds at program start. This is fixed in wine-1.1.31.
  2. However, there is no need to cache font metrics at all as Wine should find a !FreeType library greater than 2.0.5 because one is included in MacOS. If your Wine exhibits this problem, you probably need to set the DYLD_FALLBACK_LIBRARY_PATH environment variable before launching Wine.

Start wine (in a Terminal) as follows:

or

You may patch the main wine launcher yourself and forget about this variable. Save this patch file, then invoke patch -p1 < mypatch.txt in a Terminal, while at the top of Wine's source directory, see macOS/Building.

Both MacPorts and Fink use a wrapper to the wine launcher which sets exactly this variable.

14 If I have a problem with Darwine on macOS, where should I report the bug?

Since

  • Darwine is a separate project with different licensing terms from Wine (GPL vs. LGPL),
  • it's not clear what kind of patches they apply on top of Wine,
  • the fact that they insist on a different name,

- report all bugs to Darwine developers.

15 How do I switch between the Mac/X11 drivers?

As of 1.5.28, the Mac driver is the default driver. If on an older release, you can force using the Mac driver by either:

Running Windows Programs On Mac OS X Using WineHQ


How To Get Wine Working On Catalina? - Ask Different

Or by editing the registry key 'graphics' under HKCUSoftwareWineDrivers. It should specify the load order, e.g., 'mac,x11'

See Full List On Wiki.winehq.org

Retrieved from 'https://wiki.winehq.org/index.php?title=MacOS_FAQ&oldid=3352'