Legacy components for Xcode 4-12 (deprecated compilers and Mac OS X SDKs).
Home page: https://github.com/devernay/xcodelegacy
Many components were removed in recent versions of Xcode, the most notable being the Mac OS X 10.6 SDK, which is required to build software using the Carbon API (such as wxWidgets 2.8).
I made the script XcodeLegacy.sh to extract these components (the links work if you sign in to Apple Developer first) from Xcode 3.2.6 (10.4, 10.5 and 10.6 SDKs, PPC assembler, GCC 4.0 and 4.2, LLVM-GCC 4.2), Xcode 4.6.3 (10.7 SDK), Xcode 5.1.1 (10.8 SDK), Xcode 6.4 (10.9 and 10.10 SDKs), Xcode 7.3.1 (10.11 SDK), Xcode 8.3.3 (10.12 SDK), Xcode 9.4.1 (10.13 SDK), Xcode 10.3 (10.14 SDK) Xcode 11.7 (10.15 SDK) and install them in Xcode 4-12:
- GCC 4.0, GCC 4.2 and LLVM GCC 4.2 compilers
- GCC 4.0, GCC 4.2 and LLVM GCC 4.2 Xcode plugins
- PPC assembler
- Mac OS X SDK 10.4u, 10.5, 10.6, 10.7, 10.8, 10.9, 10.10, 10.11, 10.12, 10.13, 10.14, 10.15
The script also fixes a few known bugs in the 10.4, 10.5 and 10.6 SDK.
Note: There may be similar tips to compile for older iOS (not Mac OS X) versions, but I don't develop for iOS. However, if you want to enhance the XcodeLegacy script to also include those components, I'll gladly integrate your modifications.
XcodeLegacy.sh (previous versions: 1.0, 1.1, 1.2, 1.3, 1.4, 1.5, 1.6, 1.7, 1.8, 1.9, 2.0, 2.1, 2.2)
Open a Terminal application, change to the directory where XcodeLegacy.sh, and make it executable, as in:
cd path/to/xcodelegacy
chmod +x XcodeLegacy.sh
Execute the script by typing ./XcodeLegacy.sh <arg>. The script takes one argument, which can be "buildpackages" (to extract components from the legacy Xcode downloads to the current directory), "install" (to install the components in Xcode 4-10), "cleanpackages" (to delete the extracted components from the current directory), "uninstall" (to uninstall the components from Xcode 4-10).
With the "install" or "uninstall" arguments, the script uses sudo to become root, and will thus ask for your password. Please check the script contents before executing it.
Optionally, one of the following options can be passed as the first argument to XcodeLegacy.sh, to limit its operation:
-compilers: only install the gcc and llvm-gcc compilers, as well as the corresponding Xcode plugins-osx104: only install Mac OSX 10.4 SDK-osx105: only install Mac OSX 10.5 SDK-osx106: only install Mac OSX 10.6 SDK-osx107: only install Mac OSX 10.7 SDK-osx108: only install OSX 10.8 SDK-osx109: only install OSX 10.9 SDK-osx1010: only install OSX 10.10 SDK-osx1011: only install OSX 10.11 SDK-osx1012: only install OSX 10.12 SDK-osx1013: only install OSX 10.13 SDK-osx1014: only install OSX 10.14 SDK-osx1015: only install OSX 10.15 SDK-path=path: install to custom Xcode at 'path'
To use any of the older SDKs, you should:
- compile and link with the options
-mmacosx-version-min=10.5 -isysroot /Developer/SDKs/MacOSX10.5.sdk - set the environment variable
MACOSX_DEPLOYMENT_TARGETto the proper value (e.g. 10.5) and also setSDKROOTto the location of the SDK - these should be redundant with the-mmacosx-version-minand-isysrootcompiler options, but older compilers do not seem to pass this option to the linker.
For example:
env MACOSX_DEPLOYMENT_TARGET=10.6 SDKROOT=/Developer/SDKs/MacOSX10.6.sdk clang -arch i386 -arch x86_64 \
-mmacosx-version-min=10.6 -isysroot /Developer/SDKs/MacOSX10.6.sdk main.c -o main
When using a Makefile-based build, similarly set the environment variables and use the compilation flags both at compile-time and at link-time (these should typically be added to the CFLAGS and LDFLAGS in the Makefile).
When using a GNU configure-based project, pass these flags to the configure script, as in:
./configure CFLAGS="-g -O2 -mmacosx-version-min=10.6 -isysroot /Developer/SDKs/MacOSX10.6.sdk" \
CXXFLAGS="-g -O2 -mmacosx-version-min=10.6 -isysroot /Developer/SDKs/MacOSX10.6.sdk" \
LDFLAGS="-mmacosx-version-min=10.6 -isysroot /Developer/SDKs/MacOSX10.6.sdk"
When using Xcode, set the "Base SDK" and "macOS Deployment Target" build settings of the project to the right version. Perhaps a better option is to use the command-line utility xcodebuild to build using these values, rather than modifying the Xcode project file itself, as in:
xcodebuild MACOSX_DEPLOYMENT_TARGET=10.6 SDKROOT=macosx10.6 GCC_VERSION=4.2 CLANG_CXX_LIBRARY=libstdc++ \
ARCHS="ppc7400 ppc64 i386 x86_64"
Useful values for GCC_VERSION are 4.0, 4.2, com.apple.compilers.llvmgcc42, com.apple.compilers.llvm.clang.1_0. You can use GCC 4.2 or LLVM GCC 4.2 with the 10.4 SDK by passing the CC and CXX options too, as in GCC_VERSION=4.0 CC=gcc-4.2 CXX=g++-4.2.
Valid archs are ppc, ppc7400 (PowerPC G4, minimum CPU requirement to run 10.5), ppc7450, ppc970 (PowerPC G5 32-bit), ppc64, i386, x86_64 (minimum CPU requirement to run 10.7). The dsymutil utility provided with Xcode 7 and later does not work on PPC binaries, so if the GenerateDSYMFile phase fails, just pass the additional option DEBUG_INFORMATION_FORMAT=dwarf to xcodebuild.
Links to the compilers are installed in /usr/bin (or /usr/local/bin on OS X 10.11 El Capitan and later): gcc-4.0 g++-4.0 gcc-4.2 g++-4.2 llvm-cpp-4.2 llvm-g++-4.2 llvm-gcc-4.2.
GCC 4.0, GCC 4.2 and LLVM GCC 4.2 cannot compile for OS X 10.10 or newer.
The script also fixes the Mac OS X 10.4 SDK so that it works with GCC 4.2 and LLVM GCC 4.2, and later compilers (officially, it only supports GCC 4.0).
PowerPC architectures (ppc, ppc7400, ppc970, ppc64) cannot be linked for OS X 10.7 or newer (they would be useless anyway, since PowerPC CPUs were only supported up to 10.5).
Here are the latest versions of Xcode that are known to /run/ on each OS X version (the links work if you sign in to Apple Developer first):
- Xcode 2.5 on Mac OS X 10.4 (Tiger) (*)
- Xcode 3.1.4 on Mac OS X 10.5 (Leopard) (*)
- Xcode 3.2.6 on Mac OS X 10.6 (Snow Leopard) - Xcode 4.0.2, Xcode 4.1 and Xcode 4.2 also run on Snow Leopard, but are only available to pay members (*)
- Xcode 4.6.3 on OS X 10.7 (Lion)
- Xcode 5.1.1 on OS X 10.8 (Mountain Lion)
- Xcode 6.2 on OS X 10.9 (Mavericks)
- Xcode 7.2.1 on OS X 10.10 (Yosemite)
- Xcode 7.3.1 on OS X 10.11 (El Capitan), please see note on linking below. Xcode 8.2.1 (**) also runs on OS X 10.11, but can only compile for macOS 10.12.
- Xcode 8.3.3 on macOS 10.12 (Sierra), please see note on linking below. (**)
- Xcode 9.4.1 on macOS 10.13 (High Sierra), please see note on linking below. (**)
- Xcode 10.3 on macOS 10.14 (Mojave), please see note on linking below.
- Xcode 11.7 on macOS 10.15 (Catalina).
(*) These Xcode versions were released before 26.03.2012 and may cause an "An unknown installation error" during installation, which is due to an expired certificate. Installing these may require disabling network time sync and setting the date to 01.01.2012 before installing. Network time sync may be re-enabled after install. See this stackexchange question for more details.
(**) If you downloaded these Xcode versions (8.2.1, 8.3.3, 9.4.1) before 24th October 2019 the certificate used to sign them has expired and Archive Utility will refuse to unpack them. See this TidBITS article which describes the same problem in OS installers for more details. XcodeLagacy now checks for this problem and prompts you to re-download the archives which now have updated signatures.
More information about the compilers included in each version of Xcode can be found on the MacPorts Wiki and on Wikipedia.
If targetting 10.6, the following error may appear:
For architecture x86_64: Undefinedsymbols
"_objc_retain", from: referenced
In libarclite_macosx.a ___ARCLite__load (arclite.o)
(youmeant: _objc_retainedObject maybe)
Symbol not (s) found for architecture x86_64 ld:
Error: linker command failed with exit code use 1 (-v to seeinvocation clang:)
Solution: in the Build Setting of the Project (not for the Target), set the setting "Implicitly Link Objective-C Runtime Support" to NO.
Recent versions of Xcode and ld added several options. These should already be taken care of by the stub ld script (notably -object_path_lto xxx, -no_deduplicate, -dependency_info xxx), but after an Xcode upgrade new errors may appear that are not yet handled by XcodeLegacy, like:
Running ld for ppc ...
ld: unknown option: -object_path_lto
There are two possible solutions:
- check in the file
/Applications/Xcode.app/Contents/PlugIns/Xcode3Core.ideplugin/Contents/SharedSupport/Developer/Library/Xcode/Plug-ins/CoreBuildTasks.xcplugin/Contents/Resources/Ld.xcspecif there is an Xcode setting to disable that option (LD_LTO_OBJECT_FILEin the above case) - edit
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/ldto prune the culprid option (and its argument if there is one).
The GCC in Apple SDK is actually a small binary that lauches several compilers and merges the results (see driverdriver.c). The same executable can be compiled for recent GCC versions too, see devernay/macportsGCCfixup on github, resulting in a GCC executable that can be given several architectures on the same command-line.
This bug happens when building with the 10.6 or 10.7 SDK, but targetting 10.5. The 10.5 SDK uses libstdc++.6.0.4.dylib whereas later SDKs use libstdc++.6.0.9.dylib.
It can be fixed by adding this snippet somewhere in your code:
#include <AvailibilityMacros.h>
#if defined(MAC_OS_X_VERSION_10_6) && MAC_OS_X_VERSION_MAX_ALLOWED >= MAC_OS_X_VERSION_10_6
const char* ::std::bad_typeid::what() const throw() { return NULL; }
#endif
References:
- http://lists.apple.com/archives/xcode-users/2010/May/msg00183.html
- http://stackoverflow.com/questions/12980931/how-to-ignore-out-of-line-definition-error-in-xcode-with-llvm-4-1
The problem comes from the fact that some system frameworks load the system libstdc++, which results in incompatible data structures.
After exploring various options (install_name_tool, rpath, etc.), the only solution is to set the environment variable DYLD_LIBRARY_PATH to the path of a directory where you only put a symbolic link to the newest libstdc++ from GCC (libstdc++ is guaranteed to be backward-compatible, not other libraries).
If you are building an application bundle, you should replace your executable by a small executable that sets the environment variable DYLD_LIBRARY_PATH. It can be a script (see below), or a binary (better, because it handles spaces in arguments correctly).
The setdyld_lib_path.c source code can be compiled to act as a "launcher" for your binary that correctly sets the DYLD_LIBRARY_PATH variable. See the full instructions at the top of the source file.
An alternate solution, using a shell-script (doesn't handle spaces in arguments): http://devblog.rarebyte.com/?p=157
Other references:
- http://stackoverflow.com/questions/6365772/unable-to-run-an-application-compiled-on-os-x-snow-leopard-10-6-7-on-another-m
- http://stackoverflow.com/questions/4697859/mac-os-x-and-static-boost-libs-stdstring-fail
This script is distributed under the Creative Commons BY-NC-SA 3.0 license.
- 1.0 (08/10/2012): First public version, supports Xcode up to version 4.6.3
- 1.1 (20/09/2013): Xcode 5 removed llvm-gcc and 10.7 SDK support, grab them from Xcode 3 and 4
- 1.2 (03/02/2014): Xcode 5 broke PPC assembly and linking; fix assembly and grab linker from Xcode 3
- 1.3 (07/10/2014): Xcode 6 removed 10.8 SDK, grab it from Xcode 5.1.1
- 1.4 (21/08/2015): Xcode 7 removed 10.9 and 10.10 SDKs, grab them from Xcode 6.4
- 1.5 (15/10/2015): Fixes for OS X 10.11 El Capitan (nothing can be installed in /usr/bin because of the sandbox)
- 1.6 (11/11/2015): Fix buildpackages, fix /usr/bin/gcc on recent OS X, fix download messages
- 1.7 (05/04/2016): Xcode 7.3 disables support for older SDKs, fix that
- 1.9 (16/09/2016): Xcode 8 dropped 10.11 SDK, get it from Xcode 7.3.1
- 2.0 (02/05/2017): Xcode 8 cannot always link i386 for OS X 10.5, use the Xcode 3 linker for this arch too. Force use of legacy assembler with GCC 4.x.
- 2.1 (17/01/2017): Xcode 9 dropped 10.12 SDK, get it from Xcode 8.3.3; fix compiling with GNU Ada, and many other fixes
- 2.2 (10/01/2019): Xcode 10 dropped 10.13 SDK, get it from Xcode 9.4.1
- 2.3 (27/03/2019): Added an option to install in a custom Xcode path
- 2.4 (10/02/2020): Fix for buildpackages if Xcode 8 or Xcode 9 xip have expired signatures. Also now check for stray Xcode.app if extracting Xcode 9.4.1, Fixes for changed download paths and archive names.
- 2.5 (31/04/2021): Xcode 11 dropped 10.14 SDK, get it from Xcode 10.3
- 2.6 (01/05/2021): Xcode 12 dropped 10.15 SDK, get it from Xcode 11.7
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent