Mac Os Brew

THIS PAGE HAS BEEN DEPRECATED. SEE THE SPRING 2015 SITE.

$ brew tap AdoptOpenJDK/openjdk $ brew install -cask adoptopenjdk14 Multiple major releases can be installed side-by-side. To get a list of available versions, run brew search adoptopenjdk or see the list here in the README.
Once you have Homebrew (a.k.a. Brew) installed on your machine you can run the following command in the Terminal to check the version. $ brew -v To update run the following command. $ brew update Alright, time to install PostgreSQL on Mac. Install PostgreSQL using Homebrew. In Terminal run the following command to install PostgreSQL on Mac.

Installing G++ on a Mac

For the macOS platform, you can install the Azure CLI with homebrew package manager. Homebrew makes it easy to keep your installation of the CLI update to date. The CLI package has been tested on macOS versions 10.9 and later. The current version of the Azure CLI is 2.22.1. Homebrew Cask installs macOS apps, fonts and plugins and other non-open source software. $ brew install -cask firefox Making a cask is as simple as creating a formula. I decided to setup Octopress on my Mac so that I can publish blog posts from either Windows or MacOS. I’m on OS X 10.8.2. I tried to follow the Octopress instructions for installing Ruby but ran into a few problems. Install Homebrew. Homebrew is a package manager for OS X. Open Terminal and install Homebrew.

This section is intended to get you quickly started with C++ programming on your Mac. We'll be installing GCC 4.8.1 and GDB through a tool called Homebrew. If you want an additional guide on all of the following steps (except for installing GCC), the one by Moncef Belyamani is quite helpful. When you follow it, ignore anything about installing Ruby; that is, stop after setting up git.

Homebrew

Homebrew 'installs the stuff that you need that Apple don't'. It's like Ubuntu's apt-get, where one can install packages easily from repositories. Instead of having to download, configure, and install something yourself, all you need to do is run one command, and Homebrew will take care of the rest for you.

Pre-requisites

Homebrew requires that you have either Xcode or the Xcode command line tools installed on your Mac. Xcode is a free integrated development environment similar to Eclipse designed by Apple and mainly intended for iOS development or targeting the clang compiler. In this class, we will focus on gcc.

Xcode is quite a big install, so if you do not want to install it, you can get away with just installing the Xcode command line tools. See a Stackoverflow discussion for instructions on how to install the command line tools regardless of whether you have Xcode installed.

Installing Homebrew

You need xcode command line tools to install Homebrew. It is very easy to install Homebrew. Open your terminal, and run the following command:

If this doesn't seem to do anything, try killing it (CTRL C) and running it again. Or checkout homebrew website.

GCC and GDB

Installing GCC

First of all, you should make sure that your Homebrew is up-to-date. Check to see if it is so with the following:

As mentioned before, installing packages with Homebrew is very easy. First, we will add the repository from which the GCC package is available, so that Homebrew knows where to find the package we want. The repository is at https://github.com/Homebrew/homebrew-versions.

We do this by using the brew-tap command. Keep your terminal open, and run the following command. (For more information on how brew-tap works, visit the Homebrew docs):

Next, we will actually install the GCC package. Run the following command:

It might take long time before the installation is complete. If you run into any issues, you can debug with:

When done, run the following:

Mac Os Brew Uninstall Package

The result should look like this:

USC Wireless Warning

Many people have had issues running the brew install commands while connected to USC Wireless. If you are having trouble, you can either try using a wired connection, a different wireless connection, or do the following:

Download a homebrew cache
Open Finder, press CMD (command) + SHIFT + G and type /Library/Caches/Homebrew
Extract the contents of the .zip you downloaded inside of the folder you opened in the previous step. Do not extract any of the .tar.bz2 or .tar.gz inside of the .zip folder.This should look as follows:
Run brew install gcc48 in the Terminal as instructed above.

Using G++

To compile with the newly installed G++ compiler, use g++-4.8.

(Advanced) Aliasing g++

If you prefer calling g++ directly, you can also create a bash alias, as follows:

Put these two lines at the end of the file ~/.bashrc, and run:source ~/.bashrc

For more information on bash alias, take a look at the GNU Docs.

Installing GDB

Here also we use Homebrew. The following instruction has been taken from GDB on OS X Mavericks and Xcode 5 guide. To install, run the following brew command.

Check if it's installed:

The result should be gdb version 7 or higher.

Codesigning gdb

gdb is not going to debug yet. You'll get an error message like 'please check gdb is codesigned'. You need to create a certificate and sign gdb. By doing so you're telling the operating system that gdb is authorized to attach to other processes for debugging purposes. The following instructions have been taken from this Code Signing guide.

Open application 'Keychain Access' (/Applications/Utilities/Keychain Access.app)
In Keychain Access, select the 'login' keychain in the 'Keychains' list in the upper left hand corner of the window.
Open the menu item in /Keychain Access/Certificate Assistant/Create a Certificate...
Choose a name ('lldb_codesign' in the example, but you can use anything you want), set 'Identity Type' to 'Self Signed Root', and set 'Certificate Type' to 'Code Signing'. Click 'Create'.
Click continue, continue and done.
Click on the “My Certificates” category on the left side and double click on the new “lldb_codesign” certificate.
Open the context menu for 'Trust' (click the triangle) and change the following:When using this certificate: Always Trust
Now close this window, and enter your login password to confirm this change.
Option-drag (this meaning holding the option key down and dragging) the new 'lldb_codesign' certificate from the login keychain to the System keychain in the Keychains pane of the main Keychain Access window to make a copy of this certificate in the System keychain. You'll have to authorize a few more times, set it to be 'Always trusted' when asked.
Switch to the 'System' keychain and drag a copy of the 'lldb_codesign' you just made onto the Desktop.
Switch to Terminal and then run the following command (copy paste it!): sudo security add-trust -d -r trustRoot -p basic -p codeSign -k /Library/Keychains/System.keychain ~/Desktop/lldb_codesign.cer
Then right click on the 'lldb_codesign' certificate in the 'System' keychain (not 'Login') and select 'delete' to delete it from the 'System' keychain.
Then reboot your system/computer.
Finally you can sign gdb:codesign -s lldb_codesign /usr/local/bin/gdb
If this command doesn't work...then panic! Just kidding, be sure that you have gdb installed and that gdb is actually installed in /usr/local/bin. You may want to try 'which gdb' in your Terminal to figure out where it is.
Finally, remove the lldb_codesign.cer file that's sitting on your desktop, and gdb should be working at this point. :)