command line tools for xcode for mac 10.12.6

This forces developers to choose between remaining with Xcode 13, and its support back to 10.9, running in macOS Monterey, or upgrading to Ventura to run Xcode 14, but drop support for 10.9-10.12.Ĭaught in the middle are Mac users, who won’t see Apple forcing third-party developers to drop support for those older versions of OS X, but will inevitably blame the developers instead.

Neither, according to Apple’s release notes, will the current beta of Xcode 14 run in Monterey. This wouldn’t be so restrictive if Xcode 13.x were to run in Ventura, but that isn’t the case, at least as far as 13.4.1 is concerned. However, Apple’s current beta-release of the successor, Xcode 14, only supports macOS from 10.13 High Sierra to 13 Ventura. Of my little utilities, for example, over 20 presently rely on Xcode’s support so they run as far back as 10.11 El Capitan. Xcode version 13.4.1, its current release, supports all versions of macOS from 10.9 Mavericks to 12.4 Monterey. Of course, when coding for macOS, developers don’t have to use Xcode, but it’s the benchmark, the only complete environment which gives full access to the features of macOS, from its primary languages Objective-C and Swift, to the App Store and notarization for independent distribution. With the release of Ventura, Apple looks set to withdraw that support from four versions, Mavericks, Yosemite, El Capitan and Sierra, leaving third-party developers to take the blame.

While it hasn’t provided any general updates to it since September 2014, and its last Security Update was back in July 2016, third-party developers can and do build their products for Mavericks using Apple’s Xcode SDK. It may not be obvious, but Apple still supports OS X 10.9 Mavericks.

Command line tools for xcode for mac 10.12.6