Skip to content

IOS embed a dynamic framework xcode project changes #1944

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

Open
wants to merge 1 commit into
base: develop
Choose a base branch
from

Conversation

lcsatchell
Copy link

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.

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
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant