Update iOS CoreCLR runtime sample to use Release configuration #121407
+5
−5
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
github-actions
bot
added
the
needs-area-label
kotlarmilos
added
os-ios
Contributor
|
Tagging subscribers to this area: @BrzVlad, @janvorli, @kg |
Contributor
There was a problem hiding this comment.
Pull Request Overview
This PR updates the iOS CoreCLR Interpreter build configuration from Checked to Release and removes trailing whitespace from a comment.
- Changed CoreCLR Interpreter build from Checked to Release configuration for consistency with other iOS builds
- Cleaned up trailing whitespace in a comment
This was referenced Nov 6, 2025
Open
matouskozak
approved these changes
Nov 6, 2025
LoopedBard3
approved these changes
Nov 6, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Description
This PR updates iOS CoreCLR runtime sample to use Release configuration in performance pipeline and extra-platforms. This should fix the app build error caused by mismatched build configurations.