Xcode is the tool developers use to build apps for the Apple ecosystem – MacOS, iOS, and all things Apple. This guide will walk you through how to successfully install Xcode onto your Mac, from start to finish. Here are some handy tips to know before you get started: Xcode only. From MacOS Monterey, Big Sur, Catalina, Mojave, High Sierra, Sierra, OS X El Capitan, Yosemite, Mavericks onward, this is now easily possible directly and without installing the entire Xcode package first, no developer account is required either. To develop Flutter apps for iOS, you need a Mac with Xcode installed. Install the latest stable version of Xcode (using web download or the Mac App Store). Configure the Xcode command-line tools to use the newly-installed version of Xcode by running the following from the command line. After installing Catalina, Xcode refuses to install. It downloads for a long time (slow downloads from Apple) and then refuses to install with no explanation. 'Unable to Download App' “Xcode” could not be installed. Please try again later. Installing Xcode provides the C compiler that is used by Qt Creator. To choose the correct Xcode installation, you need to know your macOS version. Select menu - 'About This Mac' and read the macOS version number. If your macoS version is Catalina = 10.15, you can install the latest Xcode directly from the App Store by following these steps.
When you try to build xdebug on macOS Catalina you will get errors like these:
Configure and build xdebug on macOS Catalina
The reason for these errors is that the /usr/include folder is missing because Apple removed it when they released Xcode 11.
But, you can work around this problem. Here is how:
First, you need to make sure that Xcode and the command line tools installed. Open a terminal window and run the following command to display the SDK path:
This command should output something like this:
If not, install the command-line tools with executing:
and follow the instructions. After the installation is finished, start Xcode App to make sure the installation is done.
Now try to display the SDK-Path again:
The php tools needed to compile an extension try to use this missing include folder. We will create a modified version of phpize and php-config which will use the includes from the macOS SDK. First we will copy phpize and php-config and then we will modify these copies with a patch.
We create a new folder in your home directory under /Users/YOUR-USERNAME with the name 'php-private'..
Now copy phpize and php-config to php-private
Now determine which PHP version is installed on your system by executing
You should get something like this
I have prepared two patches to simplify the process. Download the two files and save them in your Downloads folder.
Download the phpize patch phpize-catalina.patch.zip and save it. The contents of the patch file for reference:
For PHP 7.3.9 Download the php-config patch php-config-7.3.9-catalina.patch.zip and save it.
For PHP 7.3.11 Download the php-config patch php-config-7.3.11-catalina.patch.zip and save it.
The contents of the patch file for reference:
Extract the compressed patch files.
PHP 7.3.9:
PHP 7.3.11:
Now we patching our copy of phpize and php-config
PHP 7.3.9:
PHP 7.3.11:
We are ready to compile xdebug
Create a working directory in your home folder. We will build xdebug here
Download xdebug from Xdebug.org and save in under Downloads.
Copy the archive to the working directory and extract it.
Now, we run our patched phpize in the xdebug folder.
When everything went good, you get something like this:
If so, you can skip the next part and continue with configuring and installing Xdebug.
Errors like these means, you need to install some requirements.
If phpize prints lines like these, you need to install autoconf:
To install autoconf, execute the following commands:
Now run our patched phpize in the xdebug folder again.
Check the output, and if everything went good, continue.
Configure and build xdebug:
Now we will find the full path to our patched php-config. This can be done like this:
The output will something like:
Replace '/Users/YOUR-USERNAME/php-private/php-config' with the output of the above command and configure xdebug by executing:
In the output of configure you will see that the SDK path is being used:
Now build the extension
We don't executing 'make install' to install xdebug.so because the macOS System Integrity Protection (SIP) will not allow us to install xdebug to the /usr/lib/extensions folder. To workaround this, we install the extension under the /usr/local folder.
Now edit your php.ini (usually under /etc/php.ini) to load the right xdebug. PHP searches for extensions in its default extension directory. Our xdebug resides outside of this directory, so we have to specify the full path:
To test it, execute:
The output should begin like this:
Restart your apache web server to activate your changes
If you came here looking how to install Xcode using brew (aka Homebrew), read this part first. Otherwise, skip to the introduction.
The solution depends on your answer to this question:
- Are you planning on developing iOS or Mac applications?
If the answer is “no”, then you do not need Xcode. All you need are the standalone Command Line Tools, which you can install by reading this guide.
If the answer is “yes”, then you will need to download and install Xcode from the Apple App Store. Xcode is a Mac application built by Apple, and it cannot be installed with Homebrew.
Even if you answered “yes”, you will still need Homebrew and Ruby to install cocoapods or fastlane, for example, so you should read this guide.
Introduction
After following many outdated and incomplete instructions for setting up a web development environment on a Mac (back in March 2012), and spending a lot of time finding solutions to the problems I encountered along the way, I decided to put together this detailed tutorial.
Over time, the tools got better, and ever since Mavericks, setting up a development environment on a Mac with Apple’s standalone Command Line Tools, Homebrew, Git, a Ruby manager (such as chruby, rbenv, or RVM), Ruby, and Rails has been a fairly stress-free process that’s no longer fraught with the issues I ran into in 2012.
In fact, the whole process can now be automated via the script that I wrote for you.
While it’s certainly possible to set everything up manually, it’s not as straightforward to explain because there are more options to consider in 2021. For example, the installation instructions will differ depending on your shell (Bash, zsh or fish), or if you are using a Mac with the Apple Silicon (M1) chip versus an Intel chip.
My script is smart enough to detect your current setup and install everything in the right place.
If you prefer to do everything manually, keep reading. This tutorial is kept up to date and is guaranteed to work in 2021.
Prerequisites
Supported macOS versions:
- Big Sur
- Catalina
- Mojave
Your macOS software is up to date
Before you start, make sure you have the latest Apple software updates for your current macOS version. Check by going to System Preferences, then Software Update.
Homebrew is ready to brew
You can skip this section if you know you haven’t tried to install Homebrew yet. If you’re not sure, check the contents of the /usr/local folder (also check /opt/homebrew if you’re on a Mac with the Apple Silicon chip). Run this command in the Terminal app:
If there’s nothing in the folder, then you don’t have Homebrew.
If you’ve already installed Homebrew, you’ll want to make sure that when you run brew doctor, it says Your system is ready to brew.
If it’s not ready to brew, one of the most common issues, and the first one you should fix, is missing or outdated Command Line Tools. The outdated tools message looks like this:
Here are other variations of the outdated message:
The missing tools message looks like this:
Homebrew usually provides detailed instructions for fixing things, so read carefully and follow their instructions. Quit and restart Terminal once the CLT are installed.
If you get errors other than the ones above, read through the Troubleshooting Homebrew section at the bottom of this guide.
You don’t have RVM or rbenv installed
Back in 2012, I used to use RVM, but once I automated this process, RVM kept breaking my script, so I switched to the much simpler chruby and have been using it happily every since. chruby is not compatible with RVM and rbenv, so you’ll need to uninstall them first.
Uninstall RVM
Then delete any lines related to RVM from these files if they exist:
~/.bash_profile~/.zshrc~/.zprofile
Uninstall rbenv
Follow the rbenv uninstallation instructions, then delete any lines related to rbenv from these files if they exist:
~/.bash_profile~/.zshrc~/.zprofile
If you don’t know what the ~ means, or how to edit the files above, read my guide about how to open and edit hidden files (or dotfiles) on a Mac.
Installation
Notes on Terminal
Most of the work you’ll be doing in this tutorial will be in the “Terminal” application.The easiest way to open an application in macOS is to search for it via Spotlight.
The default keyboard shortcut for invoking Spotlight is command-Space. Once Spotlight is up, start typing the first few letters of the app you are looking for, and once it appears, select it, and press return to launch it.
If you are on an M1 Mac, make sure Terminal is NOT in Rosetta mode.
You can check by running this command once Terminal opens:
It should say arm64 if you are on an M1 Mac. If it says x86_4, that means Terminal is in Rosetta mode. The only way this could happen is if you changed the setting yourself, most likely after following incorrect or outdated advice. To turn off Rosetta, follow these instructions:
- Quit Terminal if it’s running
- Go to the Finder
- Go to the Utilities folder by pressing
shift-command-U(or select “Go” from the menu bar, then select Utilities) - Select Terminal, but don’t launch it. Just click once to select it.
- Press
command-i(or from the menu bar: “File”, then “Get Info”) - Uncheck the checkbox that says “Open using Rosetta”
- Close the Terminal Info window
- Launch Terminal
- Run
uname -m. It should now sayarm64and you can proceed with the rest of this guide.
Notes on your shell
This tutorials assumes you are using zsh. If you’re not sure, read my guide to find out which shell you are using, and replace any references to .zshrc in the steps below with .bash_profile if you are using Bash.
Step 1: Install Homebrew and the Command Line Tools
Homebrew, “the missing package manager for macOS,” allows you to easily install hundreds of open-source tools. The full installation instructions are available in the Homebrew Documentation, but you should only need to run the command that’s listed at the top of the Homebrew site:
Note that the command listed on the Homebrew site could change, so please make sure that what I have listed above is the same. If it isn’t, please let me know and I’ll update it.
Copy and paste the command into your Terminal window, press return, then read what appears in the Terminal, and pay attention to any instructions that require your input. For example, Homebrew will prompt for your macOS password. Note that Terminal does not provide visual feedback when you type your password. Just type it slowly and press return.
Homebrew also automatically installs the Apple Command Line Tools, and it usually installs them in the background, but in case this changes, pay attention if any windows appear that require your input.
Once the installation is successful, quit and restart Terminal, then check if Homebrew is ready to go:
If you get Your system is ready to brew, you can move on to Step 2. Otherwise, read what Homebrew is saying very carefully. They usually provide great instructions that you should follow. If that doesn’t help, go to the Troubleshooting section to learn how to fix errors and warnings you might run into.
On Apple Silicon Macs, Homebrew might tell you to run a few commands after the installation:
Quit and restart Terminal, then check if everything is working so far:
Step 2: Install chruby and the latest Ruby with ruby-install
Install chruby and ruby-install:
Install Ruby 2.7.2:
There is a newer version of Ruby (3.0.1), but it’s not fully compatible with some gems such as Jekyll, so I recommend 2.7.2 to get started. You can always install any other available version of Ruby, in addition to 2.7.2. That’s the advantage of using a Ruby manager like chruby. You can have multiple versions on your computer at the same time, and you can easily switch between them.
This will take a few minutes, and once it’s done, configure your shell to automatically use chruby:
For Intel Macs
For Apple Silicon Macs
Quit and relaunch Terminal, then check that everything is working:
It should say ruby 2.7.2p137.
Step 3: Configure Rubygems
Disable downloading documentation when install gems (for faster installation):
Make sure Rubygems is up to date:
Step 4: Install and configure Bundler
Install Bundler:
Configure Bundler to take advantage of your computer’s cores:
Step 5: Install any other gem you want
Congrats! You now have a working Ruby development environment. You should now be able to installs Rails, or Jekyll, or whatever gem you’ve been trying to install for the past few days!
If you got any value out of my tutorial, join the 1600+ people who are becoming confident coders through my quality guides and exclusive content in my free newsletter.
Step 6: Install Git
Git is the version control system of choice among many web developers. With Homebrew, installing Git is as easy as this:
Since we just installed Homebrew, we could have skipped brew update, but it’s a good habit to run it before installing anything with Homebrew because Homebrew is updated regularly.
Quit and relaunch Terminal, then verify the Git installation:
You should get git version 2.31.1 or later.
Next, you’ll need to configure Git with your name and email, and other important settings.
Next Steps
Once you start coding away on your computer, you will most likely need to install more tools with Homebrew. Before you do, remember to always run brew update and brew doctor to make sure your system is still ready to brew. To upgrade your existing packages, run brew upgrade. It’s important to keep your development environment up to date, and Homebrew is just one of the tools you need to remember to update.
Knowing when and how to automate is a sign of an effective engineer. Most things you do repeatedly will add up to a lot of wasted time if you don’t find ways to speed them up.
That’s why I recommend taking advantage of my script, which allows you to keep your system up to date by typing a single word in your Terminal. It does that by adding an alias, which is a shortcut for the longer command. If you’re not familiar with aliases, read my guide about how aliases can speed up your workflow.
Troubleshooting Homebrew warnings and errors
Consider starting over from scratch
Before you start looking through this list and trying to fix every warning and error, I would suggest a quick and easy solution: uninstall Homebrew and start over from scratch.
Before you do that, make a backup of everything you installed with Homebrew:
This will create a Brewfile in your ~/backups directory, which you can refer to later in case you’re missing something you need. For now, I wouldn’t worry about installing everything you used to have. It’s better to start with a clean slate, and only add things that you absolutely need.
If you installed a database with Homebrew (such as Postgres), and stored data that you need, back it up first. It is unusual to have important data stored in a local database and nowehere else, but I’m mentioning it for completeness.
Then uninstall Homebrew:
This will not completely remove all Homebrew folders, so you’ll need to finish the job:
This will prompt you for your macOS password, and then it will say:
This is expected because you can’t delete the /usr/local folder itself, but you can delete anything inside it. On a brand new Mac, the /usr/local folder already exists, but it is empty.
To verify that Homebrew was completely removed, check the contents of the /usr/local folder:
It should be empty.
If you are on an M1 Mac, you’ll also need to delete the /opt/homebrew directory:
Verify that the opt folder no longer has anything inside it:
Then go back to step 1, and after you complete this tutorial, if all your coding projects are still working, then you’re good to go. Otherwise, if you get errors because tools are missing, install them as you need them with Homebrew.
Fix brew issues one by one
In many cases, Homebrew will provide helpful instructions for dealing with warnings and errors, and I usually follow those instructions. I’ve tried to cover the most common sources of warnings and errors.
Install Xcode Catalina
If you run into an issue I haven’t mentioned, try looking it up in the Homebrew GitHub Issues, or search for the error message on DuckDuckGo. If that doesn’t help, subscribe to my newsletter and I’ll do my best to help you.
After you fix each issue, run brew doctor until you get Your system is ready to brew. Then go to Step 2.
PATH issues
If you get Warning: /usr/bin occurs before /usr/local/bin, run the command below (as recommended by Homebrew), and quit and relaunch Terminal:
Read my guide about PATH to understand why this is important.
Other similar PATH issues you might see:
Missing directory errors
sudo allows you to run commands as a user with higher access rights, which is why it prompts you for your password, and mkdir stands for “make directory.”
chown stands for “change owner,” the -R flag applies this to all nested files and directories, and whoami is a variable that represents your macOS username. You should copy and paste the commands above as is.
Permission errors
If you get /usr/local/etc isn't writable or Cannot write to /usr/local/Cellar or if it complains that any directories inside /usr/local aren’t writable, fix it with this command:
This makes you the owner of the /usr/local directory, in addition to all nested directories.
Unbrewed files
Here are examples of common warnings about unbrewed files:
If you get a warning about any type of unbrewed file (such as .pc files, or static libraries), you may need to delete them as suggested by Homebrew (unless you put them there on purpose, which is unlikely). You’ll have to delete each file it complains about one by one with the rm command. For example, to remove a file called libgd.2.0.0.dylib from /usr/local/lib, you would run this command:
In some cases, it might list a bunch of files that are all in the same directory, as in this example where something went wrong when installing Node:
In this case, you can delete the entire directory that contains the unbrewed files:
Python warnings and config scripts
A related issue is:
These most likely mean you installed Python with a tool other than Homebrew. If you think you might need this version of Python, then just ignore those warnings. Otherwise, run the command below to remove that version of Python, but read this thread first.
In general, you want to install all development tools with Homebrew.
Outdated or misconfigured Xcode
Unless you plan on building iOS or Mac applications, you don’t need Xcode. All you need are the standalone Command Line Tools, which are installed when you follow this tutorial. If you already installed Xcode, you can safely delete it (again, assuming you haven’t used it and don’t plan to use it).
So, if you get any of the errors below, delete Xcode, then run brew doctor.
Outdated Xcode
Misconfigured Xcode
Linking keg-only formula
Homebrew messages are generally very helpful and they let you know exactly what to do. In this case, it is telling you to fix the linking issue by running brew unlink, followed by the tools (or “brews”) that need to be unlinked. Here, there is only one tool that needs to be unlinked. Therefore, you should run this command:
If it listed more than one tool, you would add them to the command separated by a space, like so:
Unlinked kegs
Broken symlinks
Use brew cleanup to fix these types of warnings:
Deprecated taps
In this case, you need to add the specific cask to the brew untap command, such as:
Missing dependencies
The instructions here are straightforward:
Issues with the Git repo
Follow the instructions:
Prefix issues on Apple Silicon
Catalina Xcode Can't Install
This is caused if you installed Homebrew while running your terminal in Rosetta mode, and are now running it in native mode, or if you used arch -x86_64 while in native mode, or other types of mixing the two environments.
Install Xcode 10 Catalina
Most things you need for Ruby web development are supported in native mode now, so there’s no need to use Rosetta anymore. For more details and things to look out for, read my guide on installing a development environment on Apple Silicon.