Raise deployment targets so the project builds on Xcode 27 - #12
Merged
Merged
Conversation
Xcode 27 refuses to build the project as it stands:
error: The macOS deployment target 'MACOSX_DEPLOYMENT_TARGET' is set to
10.13.6, but the range of supported deployment target versions is 12.0
to 27.0.x.
error: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to
13.5, but the range of supported deployment target versions is 15.0 to
27.0.x.
Raises the minimums to the lowest versions Xcode 27 still accepts, 12.0 for
macOS and 15.0 for iOS. Both schemes then build clean, with no source changes
needed: the limit is what the toolchain will emit for, not anything the code
does.
This does drop support for macOS 10.13 to 11 and iOS 13.5 to 14, so it is a
breaking change for anyone embedding the framework who still targets those.
Xcode 26.6 builds the current settings fine, so this only matters once you
move to 27.
Owner
|
Yes, that is unfortunate but true. I also expect that in a few months apps built using Xcode 26 will no longer be accepted in AppStore. After that, use of Xcode 27 will become mandatory and support for macOS prior to version 12 will have to be dropped anyway. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Xcode 27 will not build the project as it stands. Both schemes fail before
compiling anything:
This raises the minimums to the lowest versions Xcode 27 still accepts, 12.0
for macOS and 15.0 for iOS. That is the whole change, six lines in
project.pbxproj. Both schemes then build clean with no source changes: the
limit is what the toolchain is willing to emit for, not anything the code
actually does.
Worth being explicit that this is a breaking change for anyone embedding the
framework who still targets macOS 10.13 to 11 or iOS 13.5 to 14. Xcode 26.6
builds the current settings fine, so this only bites once you move to 27, and
it is entirely your call whether dropping those versions is the trade you want
to make now. Happy to close this if you would rather hold the wider support and
stay on 26.6 for the time being.
Verified on Xcode 27.0 (27A266a):
xcodebuild -scheme mft -destination 'platform=macOS'andxcodebuild -scheme 'mft ios' -destination 'generic/platform=iOS'both report BUILD SUCCEEDED, with no command lineoverrides.