Do not use full path for system libraries and frameworks in .xcodeproj
#867
Conversation
This file contains 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
misl6
changed the title
.xcodeproj
misl6
force-pushed
the
fix/xcode15-framework-library-lookup
branch
from
98b2498
to
a850b8f
Compare
AndreMiras
approved these changes
Sep 23, 2023
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 15 fails to build the App if the specified full path of a system library or framework is different from the target destination.
E.g: If the target destination is a real iOS device, and the specified full path is for the Simulator, it will fail to build for the real iOS device, and vice-versa.
This PR:
.xcodeprojalso works on Simulator)zbarlightrecipe (CoreMotionis a framework, not a library)