-
-
Notifications
You must be signed in to change notification settings - Fork 13
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
Switch IOS and MacOs To Use Dynamic Libs #334
Comments
Oh! Thanks for the heads up; I had no clue SPM support was right around the corner. I'll take a look later today. Looks like a cake walk when compared to CocoaPods: https://developer.apple.com/documentation/xcode/distributing-binary-frameworks-as-swift-packages |
I almost got really lucky with this since SPM has support for remote binary targets. Only problem is that they require a So that leaves us with either:
I'm going to look into the first option to start, but will fallback to the second in case the first isn't feasible. |
Just realized I won't be able to do the Rust build on local dev machines since the Rust code lives in |
TODO:
Probably just disable the FRB code gen since it seems we can just use SPM to distribute the dylib itself |
...and SPM runs in a sandbox so I've gotta completely redo CI/CD so that we can generate a checksum ahead of time. Not super happy about it, but what can you do |
I've since realized this will just be too much of a pain to do with all of the changes needed. I'm holding out hope that Native Assets will come before CocoaPods support is removed. |
Due to difficulties with CocoaPods, IOS and MacOs currently use discouraged
ExternalLibrary.process
. Flutter3.24.0
provides support for the Swift Package Manager that may fix these issues: https://docs.flutter.dev/packages-and-plugins/swift-package-manager/for-plugin-authors#how-to-add-swift-package-manager-support-to-an-existing-flutter-pluginRef: #332 (comment)
The text was updated successfully, but these errors were encountered: