give me coffee!
WineBottler 1.7.52 is a major update which sports some thrilling new features.
Homebrew: Like our content and want to support us more directly? Help Us, Help You! To run.exe files on Mac you need to use Wine or Winebottler. Wine will let you run the exe directly, whereas Wine bottler will package the.exe into a macOS. Wineskin is a tool used to make ports of Windows software to Mac OS X. The ports are in the form of normal Mac application bundle wrappers. It works like a wrapper around the Windows software, and you can share just the wrappers if you choose. Run Windows programs on Mac. This software is nothing more than an interface for the renowned Wine, thanks to which it's possible to launch more than 13,000 compatible Windows applications on a macOS. With WineBottler we'll be able to open programs like games, or professional software. This list is identical to that of Wine.
Runs on OS X El Capitan
Probably the most important feature is the update to run on OS X El Capitan. In Apples proven one-two-combination, after the visual fixes in OS X Yosemite, we could expect a major cleanup in OS X El Capitan. Apple did this with security on its mind, so the proverb “There is the Easy Way and Then There is the Right Way” smacked the lazy dev in the face, once again.
First, Apple got rid of LD_LIBRARY_PATH and DYLD_FALLBACK_LIBRARY_PATH. Forcing us to “otool -L” and “install_name_tool -change” thru all the bins and libs of Wine to use proper @rpath relative paths for all Wine related libraries. The result is, of course, a correct linking through out the app - thank you Apple. I guess somebody has to kick you once a while to come up with proper solutions.
Then Apple implemented App Transport Security which forces us to use secure connections for interactions between Apps and web services – or to disable it. For now it is disabled in WineBottler, but I’m working hard on offering SSL connections to get this right. After all it is all about security and privacy.
Further there where some GUI/multithreading glitches (Toolbar and FilePicker dialog) that lead to crashes on El Capitan and the new Codesigning requirements that have been sorted out.
Saves up to 92% harddrive-space
Yep, this one sounds to good to be true… right? 🙂 But here we go:
A clean Wine prefix weights in about 35mb. But Wine requires big add ons like gecko (for Webservices, 50mb) and mono (for .net Apps, 200mb) by default. They might not be needed by your app, but blow up an empty prefix up to 300mb. These two add ons can now be excluded: down 84%.
Further we added an option, to remove the “c:users” directory when shipping an app. Wine will automatically add new users, when the app is run on a clients Mac.
Then you can automatically remove installer files (.msi) from your prefix before shipping – if they are no longer needed.
Lastly, we have optimized how WineBottler runs your prefixes. To this point, WineBottler will copy a prefix from the App to the folder ~/Application Support. This approach allows us to install Apps to restricted System folders, or Codesign them, without breaking the signature or having to give read and write access to the app, since the App works in the users Applications Support folder. We stick to that design, but we no longer copy, but link the files to ~/Application Support. Changes files will break the link and replace it with the new file. Unchanged files will only take up some bites, instead of a complete copy, saving nearly 50% of disk-space. THIS FEATURE IS STILL VERY NEW AND IN TESTING! So I’m more than happy to hear from you.
New Wine and mono version
Finally we included the current latest and greatest Wine: Wine changelog.
Thank you very much!
For your ongoing interest and support for this project. All dough I can’t answer all the mails, I’m always interested in feedback and suggestions. Thank you very much.
As usual: head over to winebottler.kronenberg.org and grab your copy 🙂 .
enjoy
Mike
While Wineskin has been used mainly for gaming, it is capable of running non-gaming software as well.
More Information about Wineskin
While there is a lot to Wineskin, at its core it runs Windows™ software by using Wine (www.winehq.org), which is a re-implementation of the Win32 API for non-Windows™ operating systems.
Cached
Normal Wineskin Engine builds’ Wine versions are built from Wine source code from www.winehq.org
Crossover Engine builds are built from the Wine source code used in the Crossover.
Crossover is a wonderful product by Codeweavers
Wineskin Engines use WineskinX11, a custom version of X11 (required by Wine) made from XQuartz, which is an x.org based X11 server. It does not use Apple's X11.app. You can have it use XQuartz.app instead of WineskinX11 if you so choose. Wine versions from around 1.5.26+ have a Wine Mac driver that can also be used instead of needing X11.
Wine For Os X El Capitan
All original content anywhere here on urgesoftware.com belongs to Urge Software or Wineskin, please ask permission for use.