Brew Xcode

Posted on  by admin

Remove the Xcode application. First thing to do is to remove the Xcode.app located in /Applicationswhich is taking up a huge amount of space. This is pretty easy, just move it to trash and empty your trash. Update Xcode’s path. After you remove the Xcode.app, your homebrew will have trouble finding all the command binaries. Brew bundle install Give it a bit of time — a lot if you’re installing Xcode — and just like that most/all of your favorite software is installed. All in one easy peasy command line incantation. Xcode Supported Xcode versions. Homebrew supports and recommends the latest Xcode and/or Command Line Tools available for your platform (see OS::Mac:. Beginning with Xcode 8, Apple is distributing Xcode as an xip archive. See below (or brew cask xcode info) for directions on converting the xip to a dmg After downloading the file, convert the xip to a dmg by opening a terminal to the folder where the xip.

  1. Brew Xcode
  2. Homebrew Without Xcode
  3. Brew Xcode Update
  4. Install Xcode From Command Line

Mac OS X comes with Python 2.7 out of the box.

You do not need to install or configure anything else to use Python 2. Theseinstructions document the installation of Python 3.

The version of Python that ships with OS X is great for learning, but it’s notgood for development. The version shipped with OS X may be out of date from theofficial current Python release,which is considered the stable production version.

Doing it Right¶

Let’s install a real version of Python.

Before installing Python, you’ll need to install GCC. GCC can be obtainedby downloading Xcode, the smallerCommand Line Tools (must have anApple account) or the even smaller OSX-GCC-Installerpackage.

Note

Xcode

If you already have Xcode installed, do not install OSX-GCC-Installer.In combination, the software can cause issues that are difficult todiagnose.

Note

If you perform a fresh install of Xcode, you will also need to add thecommandline tools by running xcode-select--install on the terminal.

While OS X comes with a large number of Unix utilities, those familiar withLinux systems will notice one key component missing: a package manager.Homebrew fills this void.

To install Homebrew, open Terminal oryour favorite OS X terminal emulator and run

The script will explain what changes it will make and prompt you before theinstallation begins.Once you’ve installed Homebrew, insert the Homebrew directory at the topof your PATH environment variable. You can do this by adding the followingline at the bottom of your ~/.profile file

If you have OS X 10.12 (Sierra) or older use this line instead

Now, we can install Python 3:

Brew xcode update

This will take a minute or two.

Pip¶

Homebrew installs pip pointing to the Homebrew’d Python 3 for you.

Working with Python 3¶

At this point, you have the system Python 2.7 available, potentially theHomebrew version of Python 2 installed, and the Homebrewversion of Python 3 as well.

will launch the Homebrew-installed Python 3 interpreter.

will launch the Homebrew-installed Python 2 interpreter (if any).

will launch the Homebrew-installed Python 3 interpreter.

Brew Xcode

If the Homebrew version of Python 2 is installed then pip2 will point to Python 2.If the Homebrew version of Python 3 is installed then pip will point to Python 3.

The rest of the guide will assume that python references Python 3.

Pipenv & Virtual Environments¶

The next step is to install Pipenv, so you can install dependencies and manage virtual environments.

A Virtual Environment is a tool to keep the dependencies required by different projectsin separate places, by creating virtual Python environments for them. It solves the“Project X depends on version 1.x but, Project Y needs 4.x” dilemma, and keepsyour global site-packages directory clean and manageable.

For example, you can work on a project which requires Django 1.10 while alsomaintaining a project which requires Django 1.8.

So, onward! To the Pipenv & Virtual Environments docs!

Homebrew Without Xcode

This page is a remixed version of another guide,which is available under the same license.

My 2016 MacBook Pro has been sitting around ignored of late. My primary work laptop has been an Acer Predator for the last year. With the production release of Big Sur, I decided to upgrade the OS the day of release. This weekend, I tried to upgrade HomeBrew and everything it had installed, but quickly ran into a big issue with the Command Line Tools (CLT) being out of date.

For those that are unfamiliar, Homebrew is “The Missing Package Manager for macOS”. Installing software that it supports is easy and it’s considered a must-have if you’re developing on macOS.

brew install <package>

Upgrading Homebrew and its packages can be done just as easily:

brew upgrade

but running this on Big Sur, with the latest version of Xcode (12.2) installed via the App Store will throw this error:

Xcode

Your CLT does not support macOS 11.0

Xcode Beta

Log into Apple’s Developer Site and download the beta of Xcode, version 12.3 as of this writing. It’s an 11.5 GB ZIP file, which will take time to download. It also took at least 30 minutes to unzip on my machine and I have an SSD. Don’t just drop it into your Applicaitons folder, you’ll need to completely remove your existing install of Xcode from the app store. Take a look at this article for details. I don’t use Xcode other than for the CLT, so be careful and make backups before you start deleting things.

Once you’ve removed the version from the app store, drag the unzipped Xcode Beta into your Applications folder and run it. You’ll have to accept the license agreement to proceed. Once it’s up and running, run your Homebrew upgrade again.

Updated Command Line Tools

Brew Xcode Update

I immediately got the same message as before. Installing this beta was reported on multiple sites to have addressed the problem, but for me it didn’t. I forgot that there was command to specially check for issues with Homebrew:

brew doctor

Among others were these messages:

Brew

Running the softwareupdate command found nothing to install. So I followed the next pair of instructions:

Since these commands start with sudo, you’ll need to enter your user password so they’ll run. Another download began and the upgraded Command Line Tools were finally installed. If this doesn’t work for some reason, go to More Downloads for Apple Developers where you can download the DMG for “Command Line Tools for Xcode 12.3 beta” (430 MB). I’m not sure if you can run that without the main Xcode beta installed, but it’s worth a try in order to avoid the other large download. If anyone is able to run that without the main beta, please let me know.

Third Time’s the Charm

And finally,

And there was much rejoicing! And I was finally able to start writing a new blog post.

Or so I thought.

Install Xcode From Command Line

Brew Xcode

Because updated software always runs perfectly the first time.

Shyeah, right. (Jekyll, I’m looking at you.)

Homebrew and Apple Silicon

If you’re experiencing any other issues with Homebrew, check their Github account before freaking out. Not everything is currently supported on Big Sur, but they’re working on it. The other massive project in progress is supporting Apple Silicon. Take a look at macOS 11.0 Big Sur compatibility on Apple Silicon for more information.

And if you can spare something, make a donation. They deserve it.