A collection of those pesky SDK folders: MacOSX10.1.5.sdk thru MacOSX11.3.sdk
Find a file
stuff i'd rather not have attributed to me 041600eda6
Update README.md
2021-05-03 15:26:25 -04:00
MacOSX10.1.5.sdk
MacOSX10.2.8.sdk
MacOSX10.3.0.sdk
MacOSX10.3.9.sdk
MacOSX10.4u.sdk
MacOSX10.5.sdk
MacOSX10.6.sdk
MacOSX10.7.sdk
MacOSX10.8.sdk
MacOSX10.9.sdk
MacOSX10.10.sdk
MacOSX10.11.sdk
MacOSX10.12.sdk
MacOSX10.13.sdk
MacOSX10.14.sdk
MacOSX10.15.sdk
MacOSX11.0.sdk Add MacOSX11.0.sdk 2020-12-21 23:05:12 +01:00
MacOSX11.1.sdk Add MacOSX11.1.sdk 2020-12-21 21:37:54 +01:00
MacOSX11.3.sdk Add MacOSX11.3.sdk 2021-05-03 15:22:03 -04:00
.gitignore
make_tarballs.sh
README.md Update README.md 2021-05-03 15:26:25 -04:00

MacOSX-SDKs

10.1.5 - 11.3

A collection of those pesky SDK folders. Compiled from various releases of Xcode.

If you don't need this entire repository, each SDK is available here.

Outdated versions: mediafire / mega.co.nz / mediafire / mega.co.nz.

Important

Modern versions of Xcode (7.3+) need you to edit the MinimumSDKVersion in this file to use older SDKs: /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Info.plist

Usage

Set the SDKROOT environment variable:

export SDKROOT=path-to-old-sdk

If you put an old SDK in a nonstandard path, Apple's hacks in /usr/bin which redirect to calling Apple's tools in the XCode installation may fail. If your build system fails to find the compiler, explicitly specify its path:

export CC="/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang"
export CXX="/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang++"

If you are building a project with CMake, using the default Unix Makefile generator may fail to find the real make binary even if you put it in your $PATH before /usr/bin. To hack around this, install Ninja in your $PATH and use the Ninja CMake generator by running your CMake configure step with:

cmake -G Ninja -S project-root-dir -B build-output-dir