Install Wine Terminal Mac

 

How to: Install Wine on Mac OS X. Mac OS X could be the best operating system ever but there's still one thing that it lacks: you can neither run any essential Windows apps, nor even install Wine to make it possible. Here we'll try to make the things clearer and help you get the world's most popular porting software on your Apple machine. Installing Wine on Mac. To install Wine on your Mac, you will need the following: macOS 10.10 (Yosemite) or above (but 10.15 Catalina is not recommended). The first step to solving a problem is knowing what it is, so without running Wine from the Terminal, you won't be able to fix it, and neither will anyone else. Running from the Dock.

  1. Install Wine Terminal Mac Command
  2. Install Wine Terminal Macbook Pro
  3. Terminal Mac Os X
  4. Where Is Terminal Mac

Translations of this page:Françaisภาษาไทย(Translators, please see Discussion page.)

Install Wine Terminal Mac Command

What is winetricks?

Winetricks is a helper script to download and install various redistributable runtime libraries needed to run some programs in Wine. These may include replacements for components of Wine using closed source libraries.

  • May 27, 2019 Now that we have everything ready, all we have to do is install Wine on Mac. Homebrew will install it for us, just type the following in the terminal: brew install wine Now, Wine will be installed on your MacOS by Homebrew. Installing and Running Windows Programs on Mac using Wine.
  • Open icon folder in terminal by selecting ‘Open in Terminal’ in its context menu. Install the icon theme by running command./install.sh -a in the pop-up terminal. Apply new themes to make Ubuntu look like Mac OS X: 1. First open terminal, and run command to install required GTK engine and Gnome Tweak Tool.
  • How to Download Wine on a Mac. RELATED: 5 Ways to Run Windows Software on a Mac There are several ways to get Wine on a Mac. The official project website at WineHQ now provides official builds of Wine for Mac OS X. However, those aren’t necessarily the best option.

Note: Although using winetricks may be very useful for getting some programs working in Wine, doing so may limit your ability to get support though WineHQ. In particular, reporting bugs may not be possible if you've replaced parts of Wine with it. See Reporting bugs after you have used Winetricks below.

Note: Some of the packages listed below may not work well with older versions of Wine. As always we recommend you use the latest version of Wine.

Getting winetricks

The script is maintained by Austin English at https://github.com/Winetricks/winetricks. The latest release is available at https://raw.githubusercontent.com/Winetricks/winetricks/master/src/winetricks. Right-click on that link and use 'Save As' to save a fresh copy.
Alternatively you can get winetricks, using the commandline, with the command:


Also, some winetricks 'packages' require a few external tools to be installed, namely: cabextract, unzip, p7zip, wget (or curl). For GUI support, either zenity or kdialog.
Linux users can usually get these via their distribution's package management system.

Using winetricks

Once you've obtained winetricks you can run it simply by typing sh winetricks at the console. You can also use ./winetricks if you chmod +x winetricks first. If run without parameters, winetricks displays a GUI with a list of available packages. If you know the names of the package(s) you wish to install, you can append them to the winetricks command and it will immediately start the installation process. For example,

will install both the corefonts and vcrun6 packages.

Options

Version 20190912 help text:

Terminal

Tip: As with all Wine commands, winetricks knows about the `WINEPREFIX` environment variable. This is useful for using winetricks with different Wine prefix locations. For example,

installs the mfc40 package in the `~/.winetest` prefix.

Tip: Users with more than one version of Wine on their system (for example, an installed package and an uninstalled Wine built from git) can specify which version winetricks should use. For example,

installs the mfc40 package using the Wine in the ~/wine-git directory.

Reporting bugs after you have used Winetricks

Please do not report bugs if you have used winetricks to install native (ie non Wine) files, as we cannot support Microsoft dlls.

Using winetricks to install gecko, mono, and fakeie6 options is acceptable for bug reports - just be sure to mention that's what you've done.

Additionally if you found it necessary to use winetricks for an application please mention it when submitting to the AppDB, mailing lists, and other Wine resources.

Reporting bugs *in* Winetricks

Winetricks has a bug tracking system at https://github.com/Winetricks/winetricks/issues, please use it. If you don't want to get an account there to file a bug, posting on the wine user forum may also eventually get noticed.

How to remove things installed by Winetricks

Terminal

It's easy to install an entire wineprefix, so by default, winetricks installs each app into its own Wine prefix, and offers an easy way to remove wineprefixes and the menu items they created.

Winetricks does not provide a way to uninstall individual apps or DLLs inside a Wine prefix. This is for several reasons, but mainly because the preferred way to uninstall anything in Wine is to simply install into a fresh Wine prefix. (Yes, it would be nice to have uninstallers for everything, but I don't need it myself. Patches welcome.)

If for some reason, you still don't want to fiddle at all with your Wine prefixes, Wine does offer a built-in Uninstaller program. Like the Windows 'Add/Remove Programs' applet though, it only recognizes programs installed by well-behaved Windows installers that respect the registry, like InstallShield or WISE. There are no guarantees it will work with a program installed by Winetricks or other installers like .msi packages.

Installing winetricks

It's not necessary to install winetricks to use it. You may choose to install winetricks in a global location so you can just type winetricks on the command line. Some Linux distributions include winetricks in their Wine packages, so you don't have to download it separately. You probably do want to follow these steps, if the distributions packaged winetricks version lags behind the current winetricks release (e.g. Debian/Ubuntu users).

To download and install your own copy of winetricks, you can install it manually like this:

To download and install the (separate) BASH completion script for winetricks:

See Also

  • http://www.cabextract.org.uk/ -- cabextract is a tool for extracting MS cabinet files under Unix environments.
  • http://mike.kronenberg.org/index.php?s=trix (Darwine now comes bundled with trix, a gui that invokes winetricks)
Retrieved from 'https://wiki.winehq.org/index.php?title=Winetricks&oldid=3461'

This tutorial is for intermediate users who want to install and useWine on their computer running macOS.You should already know the basics of how to use the command line.If you don't, read this tutorial first.

What is Wine?

Wine is awesome.No, I'm not talking about the kind you drink,I mean the kind that lets you run Windows apps without theWindows operating system.It's kind of Zen, when you think about it.Oh, and did I mention it's completely free, legal, and open source?

Nowadays, Windows and Mac play nicely together.You can install Windows and Mac side by side and switch between them usingBoot Camp, but that requiresa reboot every time, and you can only use one operating system at a time.You can also use a tool likeParallels Desktop orVMware Fusionto virtualize Windows and run it together with Mac,but virtualization is slow and it takes up a lot of memory.(Your physical computer creates an imaginary 'virtual' computer within itself,and runs Windows on that. That takes a lot of resources!)On top of that, all of these solutions require you to own a legal copyof Windows, which isn't cheap!

Wine is different. When any program runs, it requests resourceslike memory and disk space from the operating system.All that Wine does is make sure that those requests get answered so thatthe program can run correctly. As far as the program knows, everythingis going smoothly because it has everything it needs.It never even realizes that it's not running on Windows!It's simpler than emulating a whole new computer, so it's faster.Since it's just translating requests, you don't need a copy ofthe actual Windows operating system. Plus, Wine is open source,which means people are continually improving it and adding new features.And you can't beat the price!

Will My Program Work With Wine?

A lot of people discover Wine because they have one specific Windows programthat they need to use, and it's the last thing preventing them from switchingto a different operating system. So, the big question is, will it work?The short answer is: probably, but it's worth checking.

The Wine project maintains a database called theAppDB that hasuser reviews of how well specific Windows programs work under Wine.Search for your program and find out! (If it's not listed, that doesn'tnecessarily mean that it won't work — only that you're apparently tryingto use a very obscure program!)

Requirements

To install Wine on your Mac, you will need the following:

  • macOS 10.10 (Yosemite) or above (but 10.15 Catalina is not recommended)
  • Access to an Admin account, with password
  • An internet connection

To check what version of macOS you're running,click on the Apple logo on the far left side of the toolbar,select 'About This Mac', and look at your versionnumber under the big 'macOS' or 'OS X'. If it's 10.10 or higher, you're all set.

Note that Wine does not work well with macOS 10.15 Catalina. Apple removed 32-bit supportin Catalina, which is a critical part of the macOS system that almost all of Wine relies on.You can run 64-bit applications through Wine on Catalina, but very few applications for Windowsare 64-bit. If you need to use Wine, you should not upgrade to Catalina.

You need an Admin account on your Mac because only Admins can install software.You will need to be logged in to this Admin account during the installation.If there is only one account on your computer, it is an Admin account.The account must have a password: if the account has no password,the sudo utility will fail. To set or change your password,go to the Accounts section in System Preferences.

Part 1: Install Homebrew

Homebrew is a package manager that makes installingopen source programs much easier. In particular, trying to installa large program like Wine without the help of a package manager would betremendously difficult.Fortunately, Homebrew itself is simple to install: just open up theTerminal and run this command:

The Terminal will tell you what it's about to do, and ask youif you want to proceed: press Enter to do so.The Terminal may then ask for a password: this is the passwordto the Admin account on your computer. As a security measure,the Terminal does not display anything as you type, not evenasterisks (*). Type your password anyway, and press Enter. If you get somekind of error, it might be because the Admin account doesn't have apassword set. Setting a password is required.

Installing Homebrew should only take a few seconds or minutes(depending on the speed of your internet connection). When it's done,the Terminal will say that the installation was successful, and ask you torun brew doctor. Do as it suggests:

This will make Homebrew inspect your system and make sure that everythingis set up correctly. If the Terminal informs you of any issues, you'll needto fix them yourself, and then run brew doctor again to verify that youfixed them correctly. When everything is set up correctly, you'll see themessage Your system is ready to brew, and you can move on to the next partof the tutorial.

Note: If Homebrew tells you that you need to agree to the Xcode license,you can do that by running:

The Terminal window will fill up with the Xcode license:read it, type agree and hit enter to agree to the license.

Part 2: Install Wine Using Homebrew

Now we get to actually install Wine! We'll let Homebrew do all the work,all you have to do is tell it what you want with this command:

Let's break down this command into parts. brew refers to Homebrew, whichyou just installed. cask refers toHomebrew Cask,an extension to Homebrew that is used to install GUI application on yourcomputer. (GUI stands for 'Graphical User Interface'. A GUI application isan app that you can see running, as opposed to invisibly runningin the background.) install refers to the fact that you're askingHomebrew Cask to install something on your computer, and wine-stableis the name of the thing that you want it to install. Wine has a 'stable' versionand a 'devel' version: you probably want stable, since it should have fewer bugs.

When you run this command, Homebrew will start automatically downloadingand installing software onto your computer. It might start by installingsoftware that has a totally different name: that's fine! Like most complexapplications, Wine doesn't work alone -- it relies on several other pieces of software torun correctly. These are called 'dependencies', and Homebrew is smart enoughto install them for you automatically when necessary.

While it's working, Homebrew will display messages and progress bars on the Terminal to let you know what it's doing. When it's done installing Wine, it will stop displaying messages and wait for you to type in a new command. When that happens, move on to the next step!

Part 3: Install Windows Programs Using Wine

To install a Windows program, first download the installer file:it should end with .exe. Remember the location you put it, and open upthe Terminal again. cd to the location, and use ls to make sure you cansee the installer file. (Note: if you do not know what cd and ls are,you should learn how to use the command linebefore using Wine.)

Once you are in the correct directory, run the installer through Wineby running the following command in the Terminal:

Where $INSTALLER is the name of the installer file. For example,if the installer file is named setup.exe, you would run:

A window will pop up with a regular graphical Windows installer.Click through it, and you're done! /omnisphere-2-slow-to-respond-to-pro-tools-2019.html.

Part 4: Run Windows Programs Using Wine

Open up the Terminal and run this to get to your Program Files folder:

Run ls to see what programs you have installed. Pick a program,and enter its directory using cd. (If the folder has a space in it,you must type a before the space. For example, Program Files.If you're having problems, try using tab autocomplete.)There should be a file that ends in .exe: this is the program file.Type this into Terminal:

Where $PROGRAM is the name of the .exe file. For example, if the programfile is named STARCRAFT.EXE, you would run:

The program will pop up in a new window, ready to use!Enjoy using Windows on your Mac, freely and legally!

Making a Dock Icon

Many people want to be able to run Windows programs the same waythey run other programs on the Mac: by clicking an icon in the Dock.Wine isn't specifically designed to support this, but with a little trickery,we can make it do what we want.

Note: Wine prints out error messages in the Terminal when something goes wrong.By launching Windows programs via a Dock icon, you are sidestepping theTerminal, which means that if something does go wrong and Wine has to quit,it will not be able to tell you what the problem was. The first stepto solving a problem is knowing what it is, so without running Winefrom the Terminal, you won't be able to fix it, and neither will anyone else.Running from the Dock is fine as long as your program seems to be workingcorrectly, but if it crashes, the first thing you should try is running itfrom the Terminal instead: it won't prevent the program from crashing,but it will give you some clues on how to fix the problem.

In order to launch a Windows program via the Dock, we're going towrite an AppleScriptthat launches the program for us, and then putthat AppleScript in the Dock. Essentially, we're writing a program ourselves!Don't worry, it's easy enough. There is a program on your computerthat is designed for helping you write AppleScripts:it's called 'Script Editor', and you can find it in the/Applications/Utilities directory of your computer,same as the Terminal itself.

Open up the Script Editor. You should see a window with a large areayou can type in near the top: this is where you write your AppleScript.In that area, type the following text:

You'll need to replace $PATH_TO_PROGRAM with the path from theProgram Files directory to your program executable. You can see thatyou're simply telling the AppleScript to run a line of code in the Terminal:the same line of code that you could run to start your Windows program.

Install Wine Terminal Macbook Pro

Next, press the Compile button at the top of the window.The text should become colored to indicate that Script Editorunderstands what you wrote. You can also try pressing the Run buttonto run your script: it should open the Windows program successfully.

Lastly, save your script. You can give it whatever name you'd like,but be sure to select File Format: Application in the save options,and leave Startup Screen unchecked.

Open up the Finder, go to where you saved your script, and drag thatfile to your Dock. It should stay there, just like a real application — because it is a real application! However, all it does is runthat launcher command for you, so you can move the application around,rename it, or even delete it, and it won't affect the Windows programthat you're running.

Keeping Wine Up to Date

Wine is an open source program. That means that programmersaround the world are continually improving it, adding new featuresand squashing bugs. If you don't update Wine, though, it will neverget those improvements, so it's generally a good idea to check for updatesevery so often. We can use Homebrew to keep Wine up to date: it's easy!Just run this command:

With this command, Homebrew will first update itself, if any updatesare available. It will then find all the outdated software it knows about(including Wine) and upgrade them all to the latest version.Checking for updates isn't strictly necessary, as Wine runs quite wellcurrently. However, it's a good idea to run this command every few monthsor so.

Terminal Mac Os X

Uninstalling Wine and Homebrew

If you try Wine and you don't like it, uninstalling it is easy.Just run this command:

And Homebrew will helpfully remove Wine from your computer.However, in order to install Wine, Homebrew also had to install many othersmall programs that Wine relies upon to work correctly.(That's why the install process takes so long!)If you want to remove these as well,run this script:

That script will remove everthing that you installed in this tutorial,including Homebrew, Wine, and all the other programs Homebrew installedto get Wine to work correctly.

Where Is Terminal Mac

Please enable JavaScript to view the comments powered by Disqus.