Or in cases where the developer tools are already detected and found on an external drive, and the path has been set by XCode: Sudo /Volumes/SSD/Applications/Xcode.app/Contents/Developer/usr/bin/xcodebuild -license accept IMPORTANT, remember to accept the xcodebuild licenses before using a tool that depends on it, using a command like this (with your own path): Just install as described with the sudo xcode-select -install command and leave it there, it's not taking up much space anyway. So, if you use Homebrew, you're probably better off keeping the Command Line Tools installed at the default location. Homebrew apparently needs some tools found in the separate Command Line Tools package installed with sudo xcode-select -install that's missing from the regular Xcode install (I noticed this when upgrading to a new version of Python, it was still being compiled from source no matter what I tried.) If you're using Homebrew for installing packages (like many does), it seems as if Homebrew won't register that you have the CommandLineTools installed if you move theĭirectory, and will try to compile some bottles from source. When you do a $ ls -la ~ in your Terminal.

Use the same procedure as for the Xcode simulators to move the whole ~/.android directory to a place on your external drive and symlink as described, so you end up with something like:

The Android emulators are by default located somewhere beneath Sometimes a reboot might be a good thing as well. You should now be able to use and update the simulators as usual.įirst time run may throw an error, but subsequent runs should be fine. PLEASE READ THIS FIRST! Currently, this answer is only valid for systems that runs:

Mac hard drive space color