-
-
Notifications
You must be signed in to change notification settings - Fork 21.2k
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
iOS export of C++ GDExtension fails in 4.3-dev5 #90168
Comments
Could you attach the reproduction project to make testing easier? I know it's derived from our docs but it takes time to reproduce all the setup from the docs. You can remove the compiled objects/libs to keep size low. CC @bruvzg |
Here goes... building extension with: |
Most likely something wrong with extension packaging, see |
I managed to work around this problem by changing my dylibs to the framework format.
And in the
|
Tested versions
Reproducable in 4.3-dev5, 4.3-dev [29b3d9e]
Works in 4.2.1
System information
Target iOS 17.4.1, build machine MacOS 14.4.1
Issue description
iOS export of a project with a C++ GDExtension fails in Godot 4.3-dev5.
I believe it's related to the following commit [iOS export] Improve .xcframework exporting.
I had 2 problems.
Link problem during export.
Fixed in Fixed link error during export.
Runtime error on device, the libgdexample framework isn't found
Caused by the problem 1 fix.
Fixed in Frameworks converted from .dylib are embedded as "CodeSignOnCopy" in the xcode projet
Both fixes are in the following branch. 4.3-dev-ios-gdextension-link-and-dylib-failure-fix but I'm pretty sure it's not the correct way to solve the problem, but may be useful for someone until the real fix.
Steps to reproduce
Use 4.3-dev5 and the matching export templates
Follow the instructions in gdextension_cpp_example
Add the following lines to demo/bin/gdexample.gdextension
Build the extension
Export an iOS project, will fail with a link error during the export
Minimal reproduction project (MRP)
N/A
The text was updated successfully, but these errors were encountered: