Support tree artifact outputs in XCFramework rules#2785
Merged
luispadron merged 2 commits intomasterfrom Nov 11, 2025
Merged
Conversation
16daf1b to
3ded7b7
Compare
3ded7b7 to
8283163
Compare
8283163 to
fcf8323
Compare
aaronsky
approved these changes
Nov 11, 2025
adincebic
approved these changes
Nov 11, 2025
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.
Manual cherry-pick of: 3276c83
One thing i noticed was
upstreamis generating different static xcframeworks than we are, i didnt want to change that in this PR and not entirely sure which is correct.Test from upstream:
Compared to what is created in
mastertoday: