NEW: My laptop script can automate the whole setup for you.

Xcode 4.3, released on February 16, 2012, is distributed as one application bundle,, installed from the Mac App Store. Xcode 4.3 reorganizes the Xcode menu to include development tools. Xcode 4.3.1 was released on March 7, 2012 to add support for iOS 5.1. Jun 23, 2020 Step 3 – Launch Xcode 12 beta. The excitement of trying out something new is unexplainable. Let’s go ahead and launch the new Xcode beta app. There so many ways to open the app. Go to your “Application” folder and double click on the “Xcode beta” app icon.

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, as tools have improved, and with new releases of macOS, I've updated this tutorial. 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 laptop script that I wrote for you. Note that while this tutorial refers to RVM, which is what I used between 2012 and 2016, I now use and recommend chruby, which is what my script installs.

Whether you use my script that does everything for you, or set everything up manually, it's best that you start with a clean installation of macOS. If you've already tried to install a development environment, I can't guarantee that you won't run into any issues. Certain tools used in this tutorial might not be compatible with whatever you might have installed. For example, RVM is not compatible with rbenv, and MacPorts is not compatible with Homebrew.

Again, the most reliable way to get up and running is by using my script, but ifyou insist on doing things manually, note that some parts of this tutorial mightnot be up to date. One thing I'll note is that if you're on Catalina, and it'sthe only macOS that has been on your computer so far, you should probably replaceany instances of .bash_profile in this tutorial with .zshrc. To tell whichshell is active, run echo $SHELL in your Terminal. If it says bash, use.bash_profile. If it says zsh, use .zshrc. If you use my script, youdon't have to worry about any of this.

Click on your macOS version below to get started:

Historical Background

Up until February 2012, the only way you could get the Command Line Tools required for web development was via the full Xcode package, which is almost 2 GB in size. Since then, Apple started offering the Command Line Tools (CLT) as a separate, much smaller download (~118MB), which benefits those who don't plan on writing Mac or iOS apps.

There is also a third-party option, the osx-gcc-installer by Kenneth Reitz, that supports both Snow Leopard and Lion. However, it is not updated as often as the official Apple tools, and I personally ran into issues with it on Lion.

When I tried Apple's CLT for Lion back in March 2012, they weren't compatible with Homebrew:

As of August 6, 2012, the issue above is no longer present with the latest CLT for Mountain Lion, and I believe that's the case on Lion as well, but I haven't confirmed that yet. Until I do, I recommend getting the CLT from Xcode if you're on Lion, as explained in this tutorial.

The Easy Way for Mavericks and above

I've written an open source script that canset everything up for you. If you prefer to do everything manually, start with Step 2 below.

I've left Step 1 for historical purposes because it's not always reliable.Sometimes, xcode-select --install can result in an error:

On the other hand, installing the command line tools via Homebrew, as described inStep 2 below seems to work every time I've tried it.

Step 1: Download and Install the Command Line Tools

Installing the standalone Command Line Tools on Mavericks and above

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 OS X is to search for it via Spotlight. The default keyboard shortcut for invoking Spotlight is command-Space. Once Spotlight is up, just 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. See the animated GIF below for an example:

Inside the Terminal window, copy and paste (or type) the following command, and press the return key on your keyboard:

You should see the pop up below on your screen. Click Install when it appears.

Click Agree when the License Agreement appears:

Your computer will then attempt to find the software, and then will start downloading it.The following popup will appear:

Once the software is installed, click Done. That's it! You're now ready to go to Step 2.

Installing the standalone Command Line Tools on Mountain Lion

Go to and sign in with your Apple ID (the same one you use for iTunes and app purchases).

Search for 'command line tools' (in the search field on the left), then click on the latest version of 'Command Line Tools (OS X Mountain Lion) for Xcode,' and click on the the .dmg link to download it.

Once the .dmg has finished downloading, double-click on it (if it didn't already open automatically). This will mount the disk image and open a window in your Finder that looks like this:

Double-click on the 'Command Line Tools (Mountain Lion).mpkg' installer and go through the installation. Once the CLT are installed, launch the 'Terminal' application via Spotlight (as explained in Step 1), then go to Step 2.

Installing Xcode on Lion

Click on this link to Xcode on the Mac App Store, then click on 'View in Mac App Store.'

It should automatically launch the 'App Store' app on your Mac and take you the Xcode page. Click on the 'Free' button, then click on 'Install App.'

Once the installation is complete, go to your Applications folder and double-click on Xcode, then install any required components if asked to.

Go to Xcode's Preferences via the menu bar, or by pressing the command and comma keys.

Click on the 'Downloads' icon, then click on the 'Install' button next to 'Command Line Tools.'

When prompted to log in, you should be able to use the same email and password you use for iTunes and app purchases. Once the Command Line Tools are installed, quit Xcode, launch the 'Terminal' application via Spotlight (as explained in Step 1), then go to Step 2.

IMPORTANT NOTE: If you upgraded to Mountain Lion from Lion, and you already had Xcode installed on Lion, and you updated to Xcode 4.4 and updated the Command Line Tools while still on Lion, you will have to go back to Xcode and download the Command Line Tools again after upgrading to Mountain Lion.

Snow Leopard Instructions

UPDATE: A kind reader (P. Martin) pointed out that the Xcode 4.2 download for Snow Leopard is only available to those registered in the $99/year developer program. I confirmed that the latest version of Xcode for Snow Leopard available to me while signed in with a free account is 3.2.6. I have not tested this setup with Xcode 3.2.6, but I would love to hear from you if you have. Otherwise, I recommend that you upgrade to a newer version of OS X.

Go to and sign in with your Apple ID (the same one you use for iTunes and app purchases).

If you are part of the $99/year Apple developer program, search for 'xcode 4.2' (in the search field on the left), then click on 'Xcode 4.2 for Snow Leopard,' and click on the .dmg link to download it.

Otherwise, search for 'xcode 3.2', then click on 'Xcode 3.2.6 and iOS SDK 4.3 for Snow Leopard,' and click on the .dmg link to download it. As mentioned at the beginning of this section, I have not tested this tutorial with Xcode 3.2.6, so I would recommend that you upgrade to a newer version of OS X.

Once the .dmg has finished downloading, it should automatically mount the disk image and open a window in your Finder that looks like this:

Double-click on the 'Xcode' package installer. Once the installer launches, make sure all the checkboxes are checked, as shown in the screenshot below:

Click 'Continue,' and go through the rest of the installation. If the installation fails, quit the installer, then run Software Update and install any updates that it finds.

If no new updates are available, restart your computer and try installing Xcode again. Once Xcode is successfully installed, you can move on to Step 2.

Step 2: Install Homebrew

Homebrew, 'the missing package manager for OS X,' 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 follow the instructions when prompted, as highlighted in the screenshot below. Note that Terminal does not provide visual feedback when you type your password. Just type it slowly and press return.

Once the installation is successful, run the following command:

If you get Your system is ready to brew, you can move on to Step 3. 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.

Step 3: 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.

To verify:

You should get git version 2.20.1 or later.

Run brew doctor to make sure everything is still working. If your system is ready to brew, you can move on to Step 4.

Step 4: Configure Git with GitHub for Mac

Download, install, and launch GitHub for Mac.

If you don't have a GitHub account, click on the Sign Up at link in the app, then come back to the app to complete the setup. I highly recommend that you turn on two-factor authentication for your GitHub account.

Follow these steps to set up GitHub for Mac when you first launch it:

  • Click Continue
  • Enter your username and password, then click Sign In
  • Enter your two-factor authentication code (if you have it turned on)
  • Click Continue
  • Enter an email address that you want to be attached to your commits. It doesn't have to be your real email address, but if you leave this blank, Git will nag you about it every time you commit.
  • Click Continue
  • Click Done

To see this setup in action, go to the 1:26 mark in the video I created toshowcase my automated script.

Step 5: Install RVM with the latest Ruby (2.2.0) and Rails (4.2.0)

Note that I now recommend chruby and ruby-install. I've left the RVM instructions for historical purposes.

RVM stands for Ruby Version Manager, and is one of the most popular tools that allow you to install and manage multiple versions of Ruby and Rails on the same computer.

RVM has come a long way since I originally published this tutorial. As of March 30, 2013, you can now install the latest RVM, Ruby, and Rails in one step. However, because RVM installs documentation for every gem that Rails depends on, which takes forever, I recommend disabling documentation first:

Now you can install everything with one command. If you're not interested in Rails, just replace --rails with --ruby in the command below:

Read the RVM installation documentation to see all the different options you can use.

This will take a few minutes, and once it's done, quit and relaunch Terminal, then run this command:

If you get rvm is a function, that means RVM was successfully installed. If not, go to the Troubleshooting section.

To make sure the latest versions of RVM, Ruby and Rails were installed, run the commands below:


You should get rvm 1.26.10 or higher.

For Ruby

You should get ruby 2.2.0 or higher. If you get dyld: Library not loaded: /usr/local/lib/libgmp.10.dylib, that means something is wrong with the binary version of the latest Ruby. To fix it, reinstall your desired Ruby version by disabling the binary:

For Railsrails -vYou should get Rails 4.2.0 or higher.

To make sure your system is still ready to brew:brew doctorIf everything went well, you're done! Your machine is now set up with the basic tools for web development.

If you got any value out of my tutorial, I have more time-saving tips and tricks for you in my free newsletter.

Next Steps

Once you start hacking 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.

If you installed the full Xcode package, remember that when you update it via the Mac App Store, you might also need to update the Command Line Tools via Xcode's Preferences. If you installed the standalone CLT, I recommend checking for a new version once a month or so.

If you followed this tutorial because you're interested in Rails development, I recommend visiting Daniel Kehoe's excellent RailsApps Project.

If you want to install another version of Ruby besides 2.2.0, follow the instructions below.

Installing other versions of Ruby, such as 2.1.5

Before you install a version of Ruby with RVM, you should make sure you have the latest version of RVM:

Then run:

To see all the versions of Ruby installed via RVM:

This output also lets you know which version is the default and which one is the current one in use.

To use a specific version (2.2.0 in the example below) and also set it as the default version for new shell sessions:

How to install Xcode 8 on Mac Cata…   Apple Developer Forums

To verify:

The version should match that of the current Ruby in use.



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. If you run into an issue I haven't mentioned, try looking it up in the Homebrew GitHub Issues, or Google the error message. If that doesn't help, contact me 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 3.

If you get Warning: /usr/bin occurs before /usr/local/bin, run the command below (as recommended by Homebrew), and quit and relaunch Terminal:

This command takes everything between the single quotes and adds it (>>) to a file called .bash_profile in your user's root directory (~/). Every time you open a new Terminal window or tab, .bash_profile is called. The export PATH line tells your system to look in /usr/local/bin first, since that's where Homebrew installs tools.

If you get Warning: Experimental support for using Xcode without the 'Command Line Tools', you probably upgraded from Lion to Mountain Lion but didn't reinstall the Command Line Tools. See the important note in Step 1.

If you get Error: No such file or directory - /usr/local/Cellar, run the following command, which creates the /usr/local/Cellar directory:

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.'

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.

chown stands for 'change owner,' the -R flag applies this to all nested files and directories, and whoami is a variable that represents your OS X username. You should copy and paste the command above as is.

To learn more about any Unix command, type man (for 'manual'), followed by the command. For example:

If a manual is longer than a page long, it will display a : at the end to signify there is more to read. To display one additional line at a time, press return. To display an additional page at a time, press the space bar. To quit at any time, press q.

If you get Warning: Unbrewed dylibs were found in /usr/local/lib, or a warning about any type of unbrewed 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:

If you get Warning: Python is installed at /Library/Frameworks/Python.framework, or Warning: 'config' scripts exist outside your system or Homebrew directories related to Python, it most likely means 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.

If you're on Lion, you might get this:

This should fix it:

Run brew doctor to verify. Your system should be ready to brew now.

In some cases, brew doctor might show you this warning:

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:

Run brew doctor once more, and you should be ready to brew now.


If you're installing RVM on a machine that has gpg installed (which won't be the case on a new Mac), you will get a GPG signature verification failed error. Make sure to follow the instructions in the error message. At the time of this writing, you will need to run the command below to download the signatures, after which you can go back to step 5 to install RVM.

How to load RVM into your shell session as a function

Run this command:

Now that .bash_profile has been modified, it needs to be reloaded. For initial RVM installations, the preferred way to do this is to quit and relaunch Terminal. Otherwise, you can use the following command:

If all went well, you should see rvm is a function after you run this command:

Get Xcode For Mac

Previous Notes

Installing Ruby on Snow Leopard and Lion is presumably as easy as on Mountain Lion, but I haven't been able to verify that. The instructions below are based on my experience in 2012. I've left them here for reference but I'm not sure if they still apply. For example, running rvm requirements used to provide instructions specific to your environment, but now it tries to install all the requirements for you.

The screenshots below are examples of the kind of output rvm requirements would show. One is for Snow Leopard 10.6.8 with Xcode 4.2, and the other for Mountain Lion 10.8 with no Xcode:

According to the requirements, we must first install libksba. This applies to Snow Leopard, Lion and Mountain Lion.

We can do that easily with Homebrew, but first we should make sure it is up to date:

Since Homebrew is updated regularly, it's advisable to run brew update before installing anything with Homebrew.

Now we're finally ready to install Ruby 1.9.3! If you're on Snow Leopard, you need to add a flag to the command (as specified in the RVM requirements):

If you're on Lion, you need to install automake first:

Otherwise, you will get this error when installing Ruby 1.9.3:

If you're on Mountain Lion 10.8.2 with Xcode 4.5, you will need to run these commands first:

The steps above are necessary for you to be able to install Ruby gems, such as Rails. Otherwise, you will run into errors such as these:

Learn about the key features available Xcode, the integrated development environment for building apps for Mac, iPhone, iPad, Apple Watch, and Apple TV. For detailed information on updates in the latest released versions, including each beta release, see the Xcode Release Notes.

Xcode 12

Xcode 12 includes Swift 5.3 and SDKs for iOS 14, iPadOS 14, tvOS 14, watchOS 7, and macOS Big Sur.

Universal apps

  • A single macOS Universal app includes native binaries for Intel-based Macs and Apple Silicon Macs
  • “Any Mac” destination in the toolbar builds a Universal app, even on Intel-based Macs
  • Standard Architectures build setting defaults to Universal, and Xcode offers to upgrade your project if needed
  • Run and debug the Intel binary within a Universal app by selecting “My Mac (Rosetta)” on a Developer Transiton Kit (DTK) from the Universal App Quick Start Program

NOTE: The default Xcode 12 beta can be used for development of all platforms except new Apple Silicon Macs. A separate download named “Xcode 12 for macOS Universal Apps beta” contains support for macOS Universal apps, and can be run on Intel-based Macs as well as the DTK from the Universal App Quick Start Program. A future beta of Xcode 12 will support all platforms, as well as macOS Universal apps within a single product.

Refined user interface for macOS Big Sur

  • Document tabs open any type of document, including logs, asset catalogs, and UI files, in a lightweight editor tab
  • Toolbar, icons, and sidebar designs match the beautiful new aesthetic of macOS Big Sur
  • Navigator fonts track the size of the system setting or can be manually set to a custom size
  • Organizer is completely redesigned and reports new app metrics, such as hitches in animation and scrolling

Swift and SwiftUI

  • App lifecycle in SwiftUI enables entire apps to be written completely in SwiftUI for iOS, iPadOS, and macOS
  • WidgetKit built on SwiftUI makes it easy to share code for widgets that run on iOS, iPadOS, and macOS
  • SwiftUI performance is improved throughout, and new Lazy views efficiently handle enormous data sets
  • Multiplatform templates make it easy to share SwiftUI code across all Apple platforms, customized for each
  • SwiftUI Views can be turned into reusable components that appear in the Xcode library and in code completions
  • Swift Package Manager supports resources and localizations, making it great for sharing SwiftUI components
  • Improved Swift language diagnostics make it much easier to understand coding mistakes, especially in SwiftUI code

Mac Catalyst

  • Mac idiom displays your app’s user interface in 100% native Mac size and scale for total customization
  • Additional frameworks and controls are available, including HomeKit and AVCapture
  • Keyboard APIs and OS integration make it easier to completely control your app with the keyboard
  • Apps built with Mac Catalyst automatically inherit the new look and feel of macOS Big Sur

Other improvements

  • App clips target creates a small, focused experience from your app that installs quickly
  • StoreKit testing framework and transaction manager make it easy to test and debug in-app purchases

Xcode 11

Xcode 11 includes Swift 5.1 and SDKs for iOS 13, tvOS 13, watchOS 6, and macOS Catalina 10.15

This release adds many features to bring your apps to even more Apple platforms. SwiftUI is an innovative new user interface framework with a declarative Swift syntax that is easy to read, and natural to write. Amazing new preview tools let you manually type SwiftUI code, or modify the UI with rich design tools, with code and design always in sync. Get a head start on your Mac app by selecting the “Mac” checkbox in the project settings of your existing iPad app. And with support for Swift packages in Xcode 11, you can share code among all your apps, or make use of packages created by the community.



Xcode 11 includes SwiftUI, a new Swift framework and accompanying design tools that empower a whole new way to build user interfaces. Design tools in Xcode make it as easy as drag-and-drop to construct or edit your interface, all while instantly editing the exact same Swift code file you can also edit by hand. Xcode is constantly running your real app interface live to see how it behaves directly in the design canvas, or you can instantly preview your app on an attached device.

SwiftUI includes:

  • Design tools read and write the same code you edit by hand for a single source of truth
  • Declarative syntax defines your user interface as easy-to-read Swift code
  • Animations are built using simple commands that describe the action you want to see
  • Library of controls and modifiers make it easy to design and build complex interfaces
  • Share common UI code across all Apple platforms, and add custom experiences for each OS
  • Previews show an exact rendering across various device types and accessibility settings
  • Interact with your interface live in the design canvas, or on an attached device
  • Hot-swap your edits into a live view of your app to instantly see and interact with changes

SwiftUI requires iOS 13,watchOS 6,tvOS 13, or macOS Catalina. To use the SwiftUI design canvas Xcode 11 must running on macOS Catalina.

Bring your iPad app to the Mac

It is easy to bring your existing iPad app to millions of Mac users. When you click a single checkbox Xcode can transform your iPad app into a true native Mac app that performs great.

  • Click a checkbox in your iPad project adds a native Mac app, built with the macOS SDK
  • Xcode uses a single project to build iPhone, iPad, and Mac versions of your app
  • Use a single code base for all platforms, and customize parts of your app for Mac
  • Add new SwiftUI code to the existing shared UIKit code
  • Submit to the Mac App Store directly from Xcode, or notarize for outside distribution

Swift and Swift Packages

  • Swift packages are supported throughout Xcode workflows — build, debug, SCM, and more
  • Easily use Swift packages published on GitHub, Bitbucket, GitLab, or your own hosts
  • Xcode automatically retrieves and manages packages based on dependency analysis
  • Create your own packages to share code among your own apps, or to publish for the community

iOS dark mode

  • Switch between light and dark mode instantly while developing and debugging
  • Asset catalog makes it easy to control images and colors for dark and light mode


  • Editor minimap gives a bird’s eye view of your code so you can quickly jump to any section
  • Each editor view or tab has its own preview, assistant, or other complementary views
  • Split any editor pane to layout your workspace exactly as you want

See Full List On

Other improvements in Xcode 11

  • Build stand-alone watchOS apps with a much faster debugging experience
  • Simulator launches much faster and uses the GPU to accelerate Metal code
  • Test plans give you greater control of your test harness with sharable results bundles
  • Automatically generate localized screenshots using UI tests as part of your test plan
  • Source control adds support for stash and cherry pick operations
  • Debug your app under simulated device conditions such as a slow network or thermal warnings
  • Metrics tab in the Organizer shows how efficiently your app runs on customer devices

Xcode 10.2.1

Xcode 10.2 includes Swift 5 and SDKs for iOS 12.2, tvOS 12.2, watchOS 5.2, and macOS Mojave 10.14.4.

Swift 5

  • Swift 5 runtime is included as part of the OS in the latest Apple platform releases
  • App Store thins the Swift runtime from your apps for faster downloads to devices running latest OS
  • SIMD vector types are built into the standard library
  • String literals have an enhanced syntax that makes them easier to read and write
  • New Result enum type makes it easier to handle errors across asynchronous operations

Other enhancements in Xcode

  • Debugger console has a new frame variable command alias “v” that is faster than “p” or “po”
  • Playgrounds include various stability improvements and additional memory safety checks

Xcode 10.2.1 fixes a build time issue in large Swift projects, and includes additional bug fixes.

Xcode 10.1

Xcode 10.1 includes Swift 4.2.1 and SDKs for iOS 12.1, watchOS 5.1, tvOS 12.1, and macOS Mojave.

Xcode 10

Xcode 10 looks amazing in combination with Dark Mode in macOS Mojave, and makes it easy for you to adopt the new look in your macOS apps as well. Xcode 10 beta includes Swift 4.2 and beta SDKs for iOS 12, watchOS 5, tvOS 12, and macOS Mojave.

Dark Mode Interface and Mac App Support

  • All-new dark appearance throughout Xcode and Instruments
  • Asset catalogs add dark and light variants for custom colors and image assets
  • Interface Builder switches between dark and light previews of your interface
  • Debug your Mac apps in dark or light variants without changing OS settings

Source Control

  • Changes in the local repository or upstream on a shared server are highlighted directly within the editor. At a glance, you’ll see:
  • Changes made in your code.
  • Changes not yet pushed to the shared repository.
  • Upstream changes others have made.
  • Conflicts you should address before committing.
  • Support for cloud-hosted and self-hosted Git server offerings from Atlassian Bitbucket, as well as GitLab to go along with existing GitHub support.
  • Xcode offers to rebase your changes when pulling the latest version of code from your repository.
  • SSH keys are generated if needed, and uploaded to service providers for you.

Editor Enhancements

Install Xcode Mac Command Line

  • Place multiple cursors in your code editor to make many changes at once.
  • Code folding ribbon can now hide any code block surrounded by braces.
  • Over-scroll makes it easy to center the last lines of code in the middle of your screen.

Playgrounds Built for Machine Learning

  • New REPL-like model reruns your existing playground code instantly.
  • Run your code up to any specific line, or type shift-return to run the code you just added.
  • Import the Create ML framework to interactively train new models, and then write code to test the model right in the playground. When finished, drag the model into your app.

Testing and Debugging

  • Debugging symbols are downloaded from a new device five times faster than before.
  • Xcode will spawn a collection of identical Simulators to take advantage of your multi-core Mac, and fan tests out to run in parallel, completing your test suite many times faster.
  • Run tests in random or linear order.
  • Instruments automatically show OSLog signposts you add into your code.
  • Build and share your own custom instruments package to provide unique data visualization and analysis for your own code.
  • Memory debugger uses a compact layout to make it easier to investigate your memory graph.
  • Metal shader debugger lets you easily inspect the execution of your vertex, fragment, compute, and tile shader code.
  • Metal dependency viewer provides a detailed graph of how resources are used in your Metal-based app.

Uninstall Xcode On Mac

Build Performance

  • New build system enabled by default with improved performance throughout.
  • Swift compiler builds each individual file significantly faster.
  • Large Swift projects build for debugging dramatically faster when using the incremental build setting.

Xcode For Mac Download

Xcode 9.3

Xcode 9.3 includes Swift 4.1 and SDKs for iOS 11.3, watchOS 4.3, tvOS 11.3, and macOS High Sierra 10.13.4

  • New Energy tab in the Organizer window includes logs generated when your app consumes too much power
  • Swift build tasks and other commands are run in parallel more often to improve build performance
  • Swift compiler adds new code size optimization, enabled with the -Osize build setting
  • Quick access to callers is available by clicking on a symbol while holding the command key
  • Asset catalogs support AR Reference Image files that can be detected in the real-world by your ARKit apps
  • New xccov command line tool lets you inspect code coverage reports
  • Improved source editor performance when working on extremely large files

Xcode 9.2

Xcode 9.2 includes Swift 4 and SDKs for iOS 11.2, watchOS 4.2, tvOS 11.2, and macOS High Sierra 10.13.

  • Updates to the latest platform SDKs

Xcode 9.1

Xcode 9.1 includes Swift 4 and SDKs for iOS 11, watchOS 4, tvOS 11, and macOS High Sierra 10.13

  • Fixes an issue in Simulator that impacted the performance of OpenGL ES and maps
  • Improves support for iPhone X

Xcode 9.0.1

Xcode 9.0.1 includes Swift 4 and SDKs for iOS 11, watchOS 4, tvOS 11, and macOS High Sierra 10.13

  • Simulator improvements for iPhone X
  • Fixes a problem where the Test Navigator could become out of sync with available tests

Xcode 9.0

Xcode 9 includes Swift 4 and SDKs for iOS 11, watchOS 4, tvOS 11, and macOS High Sierra 10.13

  • Refactoring makes it easy to modify the structure of Swift, Objective-C, C, and C++ code
  • Code editor is blazingly fast and responsive and adds native support for Markdown syntax
  • Fix-its apply multiple improvements to your code in a single click, and can even add required protocol methods
  • New Source Control navigator and integrated GitHub accounts make it easy to manage code across a team
  • Wireless installation and debugging for iOS and tvOS apps on devices over the network
  • Simulator looks and behaves more like a real device and can simulate multiple devices at a time
  • iOS playground templates create documents that work in both Xcode and Swift Playgrounds on iPad
  • Find navigator is incredibly fast and results show up instantly
  • Project navigator automatically keeps files and groups in sync with Finder and source control
  • Xcode Server no longer requires macOS Server and can be fully configured in Xcode preferences
  • Next-generation build system improves reliability and performance when building many projects (optionally enabled)
  • Swift 4 compiler can also build Swift 3 code to enable staged migration, one module at a time
  • Latest SDKs include the Core ML framework for machine learning and ARKit for augmented reality
Coments are closed

Most Popular Posts

  • Audio Kontrol 1 For Mac Os
  • Mac For Dj
  • Ram For Apple Mac Mini 2012
  • Microsoft Fonts For Mac Os
  • Download Free Ntfs For Mac

Scroll to top