1. Wine Install On Homebrew
2. Install Wine On Homebrew Download
3. Install Wine On Homebrew Software
4. Install Wine On Homebrew App
5. Install Wine Using Homebrew

Later, I decided to install homebrew. Then, wine didn't work so I tried brew install wine, but that didn't work. So I try brew install wine: zsh: correct 'wine' to '.wine' nyae? N Warning: It appears you have MacPorts or Fink installed. Software installed with other package managers causes known problems for Homebrew. Step 1: Installing Homebrew. Homebrew is a package manager. It facilitates the installation of open source programs, including Wine, a pretty easy task. Wine is big in size, which is why it’s better to install it. To install Homebrew: Run the Terminal. In the command line, type: ruby -e “$ (curl -fsSL https://raw.githubusercontent.com. Naturally as I’d said above 32Bit is not supported in upstream wine you can use wine64. If you need 32Bit support purchase a CrossOver license for the best experience or use my wine-crossover packages that’s also available from my homebrew tap. The wine-crossover package doesn’t provide support for macOS DXVK unlike CrossOver.

Wine Install On Homebrew

Introduction

The command line interface is a non-graphical way to interact with your computer. Instead of clicking buttons with your mouse, you’ll type commands as text and receive text-based feedback. The command line, also known as a shell, lets you automate many tasks you do on your computer daily, and is an essential tool for software developers.

While the command line interface on macOS has a lot of the functionality you’d find in Linux and other Unix systems, it does not ship with a package manager. A package manager is a collection of software tools that work to automate software installations, configurations, and upgrades. Package managers keep the software they install in a central location and can maintain all software packages on the system in formats that are commonly used.

Homebrew is a package manager for macOS which lets you install free and open-source software using your terminal. You’ll use Homebrew to install developer tools like Python, Ruby, Node.js, and more.

In this tutorial you’ll install and use Homebrew on your Mac. You’ll install system tools and desktop applications from the command line interface.

Prerequisites

You will need a macOS computer running Catalina or higher with administrative access and an internet connection. While older versions of macOS may work, they are not officially supported.

Step 1 — Using the macOS Terminal

To access the command line interface on your Mac, you’ll use the Terminal application provided by macOS. Like any other application, you can find it by going into Finder, navigating to the Applications folder, and then into the Utilities folder. From here, double-click the Terminal application to open it up. Alternatively, you can use Spotlight by holding down the COMMAND key and pressing SPACE to find Terminal by typing it out in the box that appears.

To get more comfortable using the command line, take a look at An Introduction to the Linux Terminal. The command line interface on macOS is very similar, and the concepts in that tutorial are directly applicable.

Now that you have the Terminal running, let’s install some additional tools that Homebrew needs.

Step 2 — Installing Xcode’s Command Line Tools

Xcode is an integrated development environment (IDE) that is comprised of software development tools for macOS. You won’t need Xcode to use Homebrew, but some of the software and components you’ll want to install will rely on Xcode’s Command Line Tools package.

Execute the following command in the Terminal to download and install these components:

You’ll be prompted to start the installation, and then prompted again to accept a software license. Then the tools will download and install automatically.

You can now install Homebrew.

Step 3 — Installing and Setting Up Homebrew

To install Homebrew, you’ll download an installation script and then execute the script.

First, download the script to your local machine by typing the following command in your Terminal window:

The command uses curl to download the Homebrew installation script from Homebrew’s Git repository on GitHub.

Let’s walk through the flags that are associated with the curl command:

Install Wine On Homebrew Download

• The -f or --fail flag tells the Terminal window to give no HTML document output on server errors.
• The -s or --silent flag mutes curl so that it does not show the progress meter, and combined with the -S or --show-error flag it will ensure that curl shows an error message if it fails.
• The -L or --location flag will tell curl to handle redirects. If the server reports that the requested page has moved to a different location, it’ll automatically execute the request again using the new location.
• The -o switch specifies a local filename for the file. Rather than displaying the contents to the screen, the -o switch saves the contents into the file you specify.

Before running a script you’ve download from the Internet, you should review its contents so you know what the script will do. Use the less command to review the installation script so you understand what it will do'

Once you’re comfortable with the contents of the script, execute the script with the bash command:

The installation script will explain what it will do and will prompt you to confirm that you want to do it. This lets you know exactly what Homebrew is going to do to your system before you let it proceed. It also ensures you have the prerequisites in place before it continues.

You’ll be prompted to enter your password during the process. However, when you type your password, your keystrokes will not display in the Terminal window. This is a security measure and is something you’ll see often when prompted for passwords on the command line. Even though you don’t see them, your keystrokes are being recorded by the system, so press the RETURN key once you’ve entered your password.

Press the letter y for “yes” whenever you are prompted to confirm the installation.

Once the installation process is complete, you will want to put the directory Homebrew uses to store its executables at the front of the PATH environment variable. This ensures that Homebrew installations will be called over the tools that macOS includes.

The file you’ll modify depends on which shell you’re using. ZSH is the default shell on macOS Mojave and higher. The Bash shell is a popular shell that older versions of macOS used as the default, and if you’ve upgraded your OS, you may still be using Bash.

Execute the following command to determine your shell:

You’ll see either bash or zsh.

If you’re using ZSH, you’ll open the file ~/.zshrc in your editor:

If you’re using the Bash shell, you’ll use the file ~/.bash_profile:

Once the file opens up in the Terminal window, add the following lines to the end of the file:

The first line is a comment that will help you remember what this does if you open this file in the future.

To save your changes, hold down the CTRL key and the letter O, and when prompted, press the RETURN key. Then exit the editor by holding the CTRL key and pressing X. This will return you to your Terminal prompt.

To activate these changes, close and reopen your Terminal app. Alternatively, use the source command to load the file you modified.

If you modified .zshrc, execute this command:

If you modified .bash_profile, execute this command:

Once you have done this, the changes you have made to the PATH environment variable will take effect. They’ll be set correctly when you log in again in the future, as the configuration file for your shell is executed automatically when you open the Terminal app.

Now let’s verify that Homebrew is set up correctly. Execute this command:

If no updates are required at this time, you’ll see this in your Terminal:

Otherwise, you may get a warning to run another command such as brew update to ensure that your installation of Homebrew is up to date. Follow any on-screen instructions to fix your environment before moving on.

Step 4 — Installing, Upgrading, and Removing Packages

Now that Homebrew is installed, use it to download a package. The tree command lets you see a graphical directory tree and is available via Homebrew.

Install tree with the brew install command:

Homebrew will update its list of packages and then download and install the tree command:

Homebrew installs files to /usr/local by default, so they won’t interfere with future macOS updates. Verify that tree is installed by displaying the command’s location with the which command:

The output shows that tree is located in /usr/local/bin:

Run the tree command to see the version:

The version prints to the screen, indicating it’s installed:

Occasionally, you’ll want to upgrade an existing package. Use the brew upgrade command, followed by the package name:

You can run brew upgrade with no additional arguments to upgrade all programs and packages Homebrew manages.

When you install a new version, Homebrew keeps the older version around. After a while, you might want to reclaim disk space by removing these older copies. Run brew cleanup to remove all old versions of your Homebrew-managed software.

To remove a package you’re no longer using, use brew uninstall. To uninstall the tree command, execute this command:

The output shows that the package was removed:

You can use Homebrew to install desktop applications too.

Step 5 — Installing Desktop Applications

You’re not restricted to using Homebrew for command-line tools. Homebrew Cask lets you install desktop applications. This feature is included with Homebrew, so there’s nothing additional to install.

Test it out by using Homebrew to install Visual Studio Code. Execute the following command in your terminal:

The application will install:

You’ll find the application in your Applications folder, just as if you’d installed it manually.

To remove it, use brew uninstall:

Homebrew will remove the installed software:

It performs a backup first in case the removal fails, but once the program is fully uninstalled, the backup is removed as well.

Step 6 — Uninstalling Homebrew

If you no longer need Homebrew, you can use its uninstall script.

Download the uninstall script with curl:

As always, review the contents of the script with the less command to verify the script’s contents:

Once you’ve verified the script, execute the script with the --help flag to see the various options you can use:

The options display on the screen:

Use the -d flag to see what the script will do:

The script will list everything it will delete:

When you’re ready to remove everything, execute the script without any flags:

This removes Homebrew and any programs you’ve installed with it.

Conclusion

In this tutorial you installed and used Homebrew on your Mac. You can now use Homebrew to install command line tools, programming languages, and other utilities you’ll need for software development.

Homebrew has many packages you can install. Visit the official list to search for your favorite programs.

A NOTE ABOUT MAC OS 10.15 CATALINA through 11.4 BIG SUR:
Apple has decided to force 64 bit operation and is blocking unsigned software in Catalina – so Wine is much more challenging in that version. Hams are recommended to stay with Mojave for this reason. Alternately, use the commercial wine application Crossover to avoid these issues. See here if you are ready for the extra work to *try* to make Catalina Wine-friendly again.

DUE TO THE ABOVE CHANGES IN MAC OS X, THE INSTRUCTIONS BELOW *ONLY* WORK ON PRE-CATALINA VERSIONS OF OS X! IF YOU HAVE A NEWER VERSION, SEE THESE INSTRUCTIONS INSTEAD
NEW: As of Wine version 4.19 or newer, Forms and Templates, such as the ICS-213) are now working! This means Winlink Express (RMS Express) is fully functional!

Wine is a program that tricks Windows applications into thinking they are running in a full-blown Windows OS environment. It only loads bare-bones drivers and a Windows-like folder structure into a “Bottle”, so this is NOT a Windows emulator. It runs Windows apps directly in Mac OSX or Linux!

STEP 1: INSTALL HOMEBREW
Run in Terminal app:
ruby -e '$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)' < /dev/null 2> /dev/null
and press enter/return key.
If the screen prompts you to enter a password, please enter your Mac’s user password to continue. When you type the password, it won’t be displayed on screen, but the system would accept it. So just type your password and press ENTER/RETURN key. Then wait for the command to finish.
STEP 2: INSTALL WINE

Run this command in Terminal:
export WINEARCH=win32
then run this command:
brew install wine-stable

STEP 3: Install Winetricks

1. Press Command+Space and type Terminal and press enter/return key.
2. Run this command in Terminal:
   brew install winetricks
3. Run this to add a GUI for Winetricks

STEP 3: Load DotNET 3.5sp1 and Visual Basic into the Bottle

Open a window in Terminal and enter the command:

Install Wine On Homebrew Software

winetricks

A new window will appear (if it’s blank, click OK). A window with a long list of optional Windows components and common software that can be added to a Bottle. Click on “Install a Windows DLL or component” and then click OK. Scroll down and check the boxes next to “dotnet35sp1″ and ‘vb6run” then click on the “Apply” button at the bottom of the window.

After a download completes, a number of Windows installer screens will appear… always click yes or I agree, etc., to install the software. If it asks for your name, just enter any first name and click OK. When all installations are complete, you will get a message that says “Winetricks Applied Successfully”.
NOTE: If you got an error message, you will need to run Winetricks again and select “Create a new wineprefix”. In the window that pops up, select Architecture: 32 and name the prefix “Ham” or something like that. Then repeat Step 3 again.

Install Wine On Homebrew App

STEP 4: INSTALL RMS EXPRESS (and any other Windows software you like)

Download the latest version of Winlink Express (formerly RMS Express) here. Just look for the latest version of Winlink Express and click on it.

Once it downloads, unzip it and do a “Get Info” on the .exe file by Control-Click on the icon (or highlighting the icon and selecting “Get Info” in the File pull-down menu). Change the “Open with:” pull-down to “Wine” and click on the “Change All…” button so all exe files will launch under Wine. Close the Get Info window.

Now double-click the Winlink Express Installer and if all went well the program will function! There are extra steps (below) for COM Port setup if you want rig control or access to a TNC and there are also more components needed if you plan to use VARA on HF. See below.

OPTIONAL STEP A: COM PORT SETUP

Install Wine Using Homebrew

IMPORTANT: First try using COM33 for USB Serial cables for TNCs, etc. IF that doesn’t work, then try this option below:

If COM33 doesn’t work, we can create COM1 port for rig control or TNC access. SKIP THE REST OF THIS STEP IF COM33 ALREADY WORKS!

First we need to find out what our USB/Serial controller cable is named. Install the driver for your cable. Plug the cable in and bring up a terminal (Terminal app can be found in Applications/Utilities).

ls /dev

This command lists the contents of the “dev” directory. Scroll up and look for the name of the USB cable. Some common names are:

tty.SLAB_USBtoUART

tty.usbeserial

tty.ftdi_usbserial

cu.usbserial

It WILL start with either tty or cu …so if you can’t find them in the long list, try the command:

ls /dev/cu* or ls /dev/tty*

Highlight the name and copy it (we will paste it in the next step)

This command will make a symlink (aka, an alias or shortcut) for COM1 in the dosdevices folder, which points to the USB device – usually ttyUSB0 on linux, for Mac see below:

Copy the name and paste below and use your user login name and bottle name in the bolded text (replacing the brackets):

ln -s /dev/[pasted name] ~/.wine/dosdevices/com1

Just to be clear, the entire bold part of the line above including the brackets will become the name you copied, and there will be a space between the last letter of the name you paste and “~/.wine/dosdevices/com1” Once you hit the ENTER or RETURN key, that should link the device to the new virtual COM port.

Now add the COM port to the windows registry (this will make it appear in pull-down menus in RMS Express and other Windows programs running in that bottle).

sudo nano ~/.wine/system.reg

After “#arch-win32”, add the following lines (using the arrows keys to place the cursor where you want to copy/paste this) , save and exit.

[HardwareDevicemapSerialcomm] 1131331688

“COM1″=”COM1”

NOTE: If you need more than one COM port for different control cables, just repeat the process with COM2, COM3, etc.

To save these changes, hit the CONTROL and X keys, then tap Y and then tap ENTER.

If all went well, your COM port will work now! Please note that some recent changes to the Wine software MAY force your USB-serial device onto COM33 …so if the above steps didn’t work, look for COM33 in the COM Ports pull-down of your software and try that.

OPTIONAL STEP B: GETTING VARA MODE TO WORK IN WINLINK EXPRESS

For VARA support, download these components:

and place them in /Users/[user name]/Documents/Wine/drive_c/windows/system32 and if any exist, replace them. VARA won’t work without these.

TROUBLESHOOTING: If you are still having problems installing RMS Express or getting VARA to launch within the program, check to make sure you didn’t skip a step in the DotNET and Visual Basic Runtime installations. You need all those components to be working first. Also be sure you are running Wine in a folder named “Wine” in your Documents folder for any of the above instructions to work. THIS IS CASE-SENSITIVE!

If DotNET won’t install or returns any errors at all, you may be better off using the commercial “Crossover Mac” software ($39) See here