IOS embed a dynamic framework xcode project changes #1944
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
When including a dynamic framework for ios as a dependency with embed="true", adds the necessary copy files build phase and runpath searchpath to the xcode project to ensure the framework is compiled into your app. You will need to rebuild lime tools after making hte change.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This pull request updates the generated Xcode project when using embed=true with an iOS framework dependency.
Specifically, it:
Adds a "Copy Files" build phase
Updates the Runpath Search Paths
These changes ensure that dynamic framework dependencies are correctly embedded and included in the final app bundle.
Note: You’ll need to rebuild Lime tools after applying these changes.
Why this is needed:
Dynamic frameworks aren’t automatically embedded in the same way static frameworks are. This becomes particularly important when working with Swift code, which must be included in a dynamic framework.
Use case:
To include Swift code in an extension, it was added to a custom dynamic framework. That framework was then included in the extension using embed=true. Without these changes, the framework wouldn't be properly compiled into the app.