-
Notifications
You must be signed in to change notification settings - Fork 5.3k
Ship a .framework version of Mono #53370
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from 1 commit
Commits
Show all changes
24 commits
Select commit
Hold shift + click to select a range
3d876f7
WIP
akoeplinger ada980d
Merge remote-tracking branch 'origin/main' into ios-xcframework
82555d5
Copy mono-framework.framework to same build dir as monosgen
4879ec7
Copy .frameworks to bin/
9e3bc17
Ship .framework in nupkg
ff168f9
Merge remote-tracking branch 'origin/main' into ios-xcframework
f97e186
Rename mono-framework to Mono
0ee1330
Merge remote-tracking branch 'origin/main' into ios-xcframework
7d8d578
Fix framework build on non-catalyst
e97ec4c
Build stubby (release) and static-component (release) .frameworks
f16eabb
Merge remote-tracking branch 'origin/main' into ios-xcframework
75ea8d1
Strip frameworks
9bd0b0e
What if we flatten to iOS-style unversioned frameworks on non-iOS?
4ee0938
Fix stripping-dwarf-files bug
45f4e2b
Merge remote-tracking branch 'origin/main' into ios-xcframework
3315ef6
Merge branch 'ios-xcframework' of github.com:directhex/runtime into i…
8f544ab
Bundle dylibs for components on dynamic component platforms
db386ee
Only build .frameworks if explicitly turned on; turn on in relevant C…
aa31a96
Merge remote-tracking branch 'origin/main' into ios-xcframework
62ab8ae
Typo
2837fcb
Fix casing (from Mitch)
65e00a7
Add explanation of whitespace fiddling to bypass cmake list limitations
29e9413
Release and debug were reversed (debug should get full objects, not s…
bd8272e
Merge remote-tracking branch 'origin/main' into ios-xcframework
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Add explanation of whitespace fiddling to bypass cmake list limitations
- Loading branch information
There are no files selected for viewing
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this should be
TARGET_DARWIN AND STATIC_COMPONENTS.I think this version of the code is only right if the components are static archives, right?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So we should never build a .framework in the case of .dylib components? Didn't you say iOS Simulator should ship dylibs & build against stubs in #53370 (comment) ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry, I meant to me this looks like the code only supports the static components case. I assumed a dynamic components version will be added in a follow-up PR. Maybe I misunderstood what's happening here.