Has anyone tried installing Arena on a Mac using Wine? Question If I am offered entry into the closed beta I would love to test out the program, but I have a Mac.
< MacOS
Building Wine on macOS
If you just want to install a recent version of Wine, and possibly report Bugs or AppDB tests, you should be fine just following the instructions on the main macOS page for installing a WineHQ package.
If you're interested in Submitting Patches or Regression Testing though, you'll want to build Wine from the tip of WineHQ's Git repo; this page explains how to do that on macOS in more detail.
Homebrew, MacPorts, and Fink are source repositories that can make it easier to build WINE on macOS, and some notes on using them are provided below. Note, however, that they are not part of the Wine Project; any problems with Homebrew, Macports, or Fink should be reported to the respective site.
In order to build and run Wine, you might need to install some extra software. Getting it shouldn't be much trouble though.
Xcode
The Xcode development suite is the primary kit you will need, regardless of whether you decide to do a minimal build from git, use a build script, or download from one of the ports projects. A version of it will be included in the Optional Installs folder of your macOS installation DVD. You should also be able to download the latest version for your model from the Apple developer site.
Note: If you don't want to install the full suite, you should be able to make due with just the Command-Line Tools component of Xcode. This will include all of the necessary build tools and even git. Any other libraries should come pre-installed in macOS or can be pulled in automatically by other tools.
XQuartz
In the past, Wine's native Mac driver still needed a good deal of work so running Wine on macOS required installing an X11 server too. This is no longer necessary, but there are still some features missing from the Mac driver (see the to-dos on the macOS page) so you still might want to run Wine with the X11 driver.
According to Wikipedia, from v10.3 (Panther) to v10.7 (Lion) of macOS, Apple at least included a Mac-compatible X11 server as an optional install. https://generousink801.weebly.com/pioneer-ddj-sr-djay.html. However, since v10.8 (Mountain Lion), Apple has stopped providing its own release of the X11 server and advises all users to download the newest version of a compatible X11 server directly from upstream.
The open-source XQuartz project develops the Mac version of X11; you can download the disk-image file directly from there, then just use the macOS installer.
During setup, the upstream XQuartz disk-image will replace /usr/X11 (which is in most PATH variables) with a symlink to /opt/X11 (where it installs the files). However, if you upgrade your release of macOS, this symlink may get clobbered, leading to fatal errors in X11 programs. Reinstalling XQuartz will repair the link automatically, or you can manually restore it with:
If you have a supplementary package manager, you might also be able to grab XQuartz (or an equivalent port of the vanilla xorg server):
Once you have Xcode and a version of the X11 server (not required but highly recommended), you need to grab both the build and runtime dependencies for Wine. While you can just run Wine's configure script and keep installing libraries that it complains are missing, using a package manager will save you a lot of trouble and keep your system cleaner.
The main caveat with the various macOS package repos is that you do not want to mix them. Once you've decided to use one, stick with it, and if you decide to switch to a different one, it's probably best to uninstall all of your old packages first, then reinstall them with the new system.
The subsections below describe ways you can get just the necessary dependencies for Wine. If you want, you can always just install the appropriate wine package, which will pull in all the other packages you need. At that point, you can either uninstall just the wine package, or keep it and run your own build from within its directory.
Homebrew
Homebrew no longer provides a wine How to loop on garageband mac. formula instead using cask to install wine.
The following would cover basic requirements;
As homebrew no longer provides universal dylibs anything outside of XQuartz provided files and the basic build dependencies would need to be built from source
MacPorts
On MacPorts, to get all the dependencies for Wine, both build and runtime, you just want to use the rdepof: query (short for 'recursive depends of') with the install command. Unless you definitely want the stable release of Wine, use the wine-devel package to get the most up-to-date dependency list:
Please Note:
If you're running macOS High Sierra you need to install XCode 9 & XCode 9 Command Line Tools, not the versions from the App Store. If your running macOS Mojave you need to do some workarounds check https://trac.macports.org/ticket/56991#comment:70
Now with the dependencies installed, you will use almost the same procedure as described on the Building Wine page. You should be able to run ./configure and make with the same parameters as on another system.
Note: In the past on macOS, it was necessary to point to libraries and headers installed through the package managers too. However, recent versions of all the major package managers should either automatically add to your PATH variable or create symlinks into /usr/local.
You can configure your build directory to compile with clang like so:
Please Note: While Wine can be compiled using XCode on macOS (Compiling with XCode10 requires MacOSX10.13.sdk & setting min version to 10.7) , however compiling wine64 will have problems with regedit and other components so its better to cross-compile using Docker (instructions for this will be added later)
When installing Wine from source on macOS, you may need to make some quick configuration changes.
After compiling Wine from source, you can install it into /usr/local with make install, but it's highly recommended that you run it from the build directory.
Depending on how you installed XQuartz, you might see fatal errors in X11 when you try to run your own build of wine from the command-line. This is due to XQuartz installing into the /opt/X11/ directory and creating symlinks to /usr/X11/, neither of which is typically checked by the macOS dynamic linker. There are a couple of workarounds for this:
However, this second approach is more tedious to undo and may be more fragile in some situations.
You might need to tweak the actual directories in your list, but you can avoid the tedium of typing the list every time by setting it in one of your shell config files (e.g. .profile, .bash_profile, or .bashrc):
Joerg Hoehle proposed patching the winewrapper to adjust DYLD_FALLBACK_LIBRARY_PATH every time wine is invoked. For some reason, the patch was rejected (perhaps changing PATH variables or symlinking should be done upstream by XQuartz?)
Retrieved from 'https://wiki.winehq.org/index.php?title=MacOS/Building&oldid=3559'
The following instructions are heavily inspired by /u/uhohohdear.
IMPORTANT UPDATE: ~~ WOTC just released a new executable that should work with these original directions. I updated the download link below.
Dependencies
Note: If you're like me, you may not trust unofficial Wineskin wrappers. Unfortunately, the Wineskin project is way behind and only supports Wine 2.x. We need at least Wine 3.0 to run MTGA. If Wineskin ever gets around to updating, you can get the official download here.
Installing MTGA
Note: The wrapper has 'Screen Options' and then 'Auto Detect GPU Info for Direct3D' unchecked and 'Use Mac Driver instead of X11' checked. If you complete installation of MTGA and are getting DirectX 11 errors, come back to this step and change these settings, but the defaults sjould work.
You can now click 'Quit' and start playing MTGA! If you'd like to add Retina support, carry on.
Adding Retina/HiDPI Support
Note: You can find your screen's dpi on Apple Support or via DPI Love.
You can now close Wineskin and start playing MTGA in high resolution!
FAQSMagic The Gathering For Mac Os Installing With Wine BarI'm getting a DirectX 11 error and it's making me sad.
This wrapper already includes the fixes below, so you should not have these issues.
Repeat steps 0 and 1 under 'Installing MTGA' and trying unchecking 'Auto Detect GPU Info for Direct3D' and checking 'Use Mac Driver instead of X11'. If you're still having problems, use TextEdit to create a plaintext file (use
shift+command+T to toggle between rich text and plaintext) with the following information:
Save this file as
d3d.reg . Go to /Applications/ then right click/control click the Wineskin wrapper (MTGArena.app) and select 'Show Package Contents'. Open 'Wineskin.app'. In Wineskin, click 'Advanced', select 'Tools', and then click 'Registry Editor (regedit)'. From the 'Registry' menu, choose 'Import Registry File..' and select the d3d.reg file you just created. Close regedit, exit Wineskin, and try running MTGArena again.
I'm playing MTGA in windowed mode and, after switching to another program, it stops responding.
Everything is fine. Just grab the MTGA window and wiggle it a little bit. Everything should be back to normal.
I tried to launch MTGA and I get some error that crashes the program!
Again, the fix for this is already applied but I left the question in the FAQ, you should not have this issue with this wrapper.
This is a common issue with running MTGA in Wine. Close the program and wait a few seconds. It should work fine on the second attempt. ¯_(ツ)_/¯
Magic The Gathering For Mac Os Installing With Wine Glasses
If this really bugs you, here's a fix so that MTGA will launch perfectly every time:
Note: If you're using TextEdit, make sure you've turned off the option to add a .txt file extension.
There's an Arena update and nothing works anymore!
Yeah. It's annoying. You will need to download a new msi and reinstall.
Comments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |