如何构建可分发至不同OS X/macOS版本的C++应用及相关疑问

Great question—this is a super common pain point when distributing C++ apps across macOS versions, especially with the ABI shifts in Clang/libc++ over the years. Let’s break this down clearly:

关键C++ ABI破坏节点 #

First, let’s nail down which compiler/Xcode versions introduced breaking ABI changes (these are the lines you don’t want to cross between build and target systems):

• Xcode 8 (Clang 3.8)：This was a major shift—Apple switched from the old GCC-compatible libstdc++ to libc++ as the default C++ standard library, and fully adopted the C++11 ABI. Apps built with Xcode 8+ are not compatible with those built with Xcode 7 or earlier.
• Xcode 10.2 (Clang 7.0)：Apple updated the internal implementation of std::string and std::list in libc++, creating another ABI break. Apps built with Xcode 10.2+ won’t run properly on systems where the system libc++ doesn’t match this new implementation (pre-10.14 macOS versions).

按目标OS版本匹配Xcode #

To ensure compatibility, you’ll need to use specific Xcode versions for each target macOS range:

• Target: OS X 10.9–10.11 (Mavericks to El Capitan)

  • Use Xcode 7.3.1: This is the last Xcode version that fully supports these old OS versions. It uses the legacy libstdc++ ABI, which is required for apps to run on these systems—newer Xcode versions’ libc++ builds will crash here even with a low deployment target set.
  • Note: C++11/14 support is partial in this Xcode version, so you may need to adjust your code if you rely on newer features.

• Target: macOS 10.12–10.13 (Sierra to High Sierra)

  • Use Xcode 9.4.1: This version uses the stable libc++ ABI from the Xcode 8–10.1 era, which is compatible with these OS versions. Avoid Xcode 10.2+ here—its updated libc++ will cause runtime errors on 10.12/10.13.

• Target: macOS 10.14–10.15 (Mojave to Catalina)

  • Use Xcode 11.7: This is the last Xcode version that supports these OS versions natively, and its libc++ ABI matches the one introduced in Xcode 10.2. It also has solid C++17 support, and can build universal binaries for x86_64 (and run via Rosetta on Apple Silicon if needed).

• Target: macOS 11+ (Big Sur, Monterey, Ventura, etc. including Apple Silicon)

  • Use Xcode 13+ (stable releases like 14.3.1): These versions have a stable libc++ ABI, full support for modern C++ standards (C++20/23), and native Apple Silicon (arm64) compilation. The ABI here is consistent across all 11+ macOS versions, so you won’t run into cross-version compatibility issues.

重要注意事项 #

• Third-party library compatibility: If you link against pre-built C++ libraries, make sure they were compiled with the same Xcode version you’re using. Mismatched ABIs will cause linker errors or silent runtime crashes.
• Deployment target isn’t enough: Setting MACOSX_DEPLOYMENT_TARGET to an older version doesn’t override ABI differences. A high-Xcode build will still rely on newer libc++ symbols that don’t exist on older OS versions.
• Universal binaries: For x86_64 + arm64 support, use Xcode 12+ if targeting macOS 11+, or Xcode 11.7 if you need to include 10.15 support.

内容的提问来源于stack exchange，提问作者Altair