[draft] Update AppleAppBuilder to use dynamic components on iOSSimulator #54241
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
|
@lateralusX @akoeplinger just dumping my WIP. This is enough to build a helloworld sample that tries to use something from the hot reload component, but it's needs to be less hacky. |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
|
/azp run runtime-staging |
|
Pull request contains merge conflicts. |
lambdageek
force-pushed
the
ios-appbuilder-dynamic-components
branch
from
5cb8a81 to
3f085c7
Compare
ghost
closed this
|
Draft Pull Request was automatically closed for inactivity. Please let us know if you'd like to reopen it. |
ghost
locked as resolved and limited conversation to collaborators
This pull request was closed.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
WIP.
We want to load components dynamically.
One issue is that we must link against a dynamic libmonosgen-2.0.dylib so that the components can resolve the mono symbols. (It's possible there's some way to use
install_name_toolto change the reference to@rpath/libmonosgen-2.0dylibto the app instead).Currently this just drops all the component dylibs into the app bundle, but we should instead only copy the ones that are specified in the
RuntimeComponentstask property.