How To Install Gcc On Mac

Installing G++ on a Mac

This section is intended to get yous quickly started with C++ programming on your Mac. Nosotros'll be installing GCC 4.eight.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 y'all follow it, ignore anything about installing Scarlet; that is, finish after setting up git.

Homebrew

Homebrew "installs the stuff that you need that Apple tree don't". It's like Ubuntu's apt-become, where one tin 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 volition 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 form, we will focus on gcc.

Xcode is quite a big install, so if y'all do non desire to install it, you tin can get abroad with just installing the Xcode command line tools. See a Stackoverflow give-and-take for instructions on how to install the control line tools regardless of whether y'all have Xcode installed.

Installing Homebrew

You need xcode command line tools to install Homebrew. It is very piece of cake to install Homebrew. Open up your terminal, and run the following control:

            ruby-red -east              "$(curl -fsSL https://raw.github.com/Homebrew/homebrew/get/install)"

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

GCC and GDB

Installing GCC

First of all, you should brand certain that your Homebrew is up-to-engagement. Check to see if it is then with the following:

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

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

            brew tap homebrew/versions

Adjacent, we will actually install the GCC package. Run the post-obit command:

It might have long time before the installation is consummate. If you run into any bug, you can debug with:

When washed, run the following:

The result should look similar this:

            gcc-4.8 (GCC) 4.8.1 Copyright (C) 2022 Free Software Foundation, Inc.

USC Wireless Warning

Many people take had bug running the mash install commands while connected to USC Wireless. If you are having problem, you lot tin can either try using a wired connexion, a different wireless connection, or practice the post-obit:

Download a homebrew enshroud
Open Finder, press CMD (command) + SHIFT + One thousand and type /Library/Caches/Homebrew
Extract the contents of the .zip you lot downloaded inside of the folder you opened in the previous step. Practice non extract any of the .tar.bz2 or .tar.gz inside of the .nothing folder. This should expect as follows:
Run brew install gcc48 in the Final equally instructed above.

Using G++

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

            g++-4.8 test.cpp -o test.out

(Avant-garde) Aliasing g++

If you adopt calling thousand++ directly, you can also create a bash alias, as follows:

            alias k++="g++-4.8" alias gcc="gcc-iv.eight"

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

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

Installing GDB

Here as well we utilise Homebrew. The following educational activity has been taken from GDB on Os 10 Mavericks and Xcode 5 guide. To install, run the following mash command.

            brew install https://raw.github.com/Homebrew/homebrew-dupes/primary/gdb.rb

Bank check if it's installed:

The result should exist gdb version 7 or higher.

Codesigning gdb

gdb is not going to debug yet. You'll go an error message like "please cheque gdb is codesigned". You demand to create a certificate and sign gdb. By doing so you're telling the operating organisation 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 mitt corner of the window.
Open the carte detail in /Keychain Admission/Certificate Assistant/Create a Certificate...
Cull a name ("lldb_codesign" in the case, but y'all can utilize anything you want), set up "Identity Type" to "Self Signed Root", and set up "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 carte 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.
Choice-drag (this meaning holding the pick cardinal downward and dragging) the new "lldb_codesign" document from the login keychain to the System keychain in the Keychains pane of the main Keychain Access window to brand a re-create of this certificate in the Organisation keychain. Yous'll accept to authorize a few more times, set information technology to be "Always trusted" when asked.
Switch to the "System" keychain and drag a copy of the "lldb_codesign" yous just fabricated onto the Desktop.
Switch to Final and then run the post-obit command (re-create paste it!): sudo security add-trust -d -r trustRoot -p basic -p codeSign -grand /Library/Keychains/System.keychain ~/Desktop/lldb_codesign.cer
And so 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/calculator.
Finally you tin sign gdb: codesign -s lldb_codesign /usr/local/bin/gdb
If this command doesn't piece of work...and then panic! Merely kidding, exist sure that you have gdb installed and that gdb is actually installed in /usr/local/bin. You may want to endeavor "which gdb" in your Terminal to figure out where information technology is.
Finally, remove the lldb_codesign.cer file that's sitting on your desktop, and gdb should be working at this signal. :)