[5.7][Immediate]: Workaround for loading Foundation in immediate mode #59731
Conversation
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
|
@swift-ci test |
|
@swift-ci test |
|
@swift-ci test |
1 similar comment
|
@swift-ci test |
|
CC: @nate-chandler |
|
@tbkka main branch PR has been merged. |
tbkka
approved these changes
Jun 29, 2022
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.
Cherry picked from #59730.
Explanation: The framework layout of Foundation has changed in 13.0, causing unresolved symbol errors to
libswiftFoundationin immediate mode when running on older OS versions with a 13.0 SDK. This workaround scans through the list of dependencies and manually addslibswiftFoundationif necessary.Scope: Immediate mode
Risk: Low
Testing: Local testing
Reviewer: @nate-chandler
Issue: rdar://94645534