Repository navigation
Add swift_versions to plugin template podspec, include default CocoaPod version - #44324
Conversation
There was a problem hiding this comment.
There's disagreement about whether to make swift_versions exact based on the plugin author's tested Swift version, or whether to make it as permissible as possible (like this). We have a meeting to make a decision one way or the other.
If we go with the former, these lines will become:
s.swift_version = '5.0'42ffaaa to
9215ae2
Compare
xster
left a comment
There was a problem hiding this comment.
LGTM, once the versioning scheme is discussed.
There was a problem hiding this comment.
What are the asserts here? Just that it built? Any file we should check for in the output build/ios directory?
There was a problem hiding this comment.
Yes, it will fail if any build commands fail. Most of these build scenarios fail on master due to CocoaPods or linker issues, which cause the build command to fail.
I think we check the output structure in other tests.
There was a problem hiding this comment.
should we just move ios.tmpl/projectName.podspec.tmpl to ios-objc.tmpl/projectName.podspec.tmpl then if ios-swift.tmpl is getting its own?
There was a problem hiding this comment.
It was renamed in this commit as well.
.../plugin/ios.tmpl/projectName.podspec.tmpl → ...in/ios-objc.tmpl/projectName.podspec.tmpl
|
I'm going to split this into 2 PRs: one for the Swift plugin template, one for the app build settings |
9215ae2 to
445a481
Compare
|
It looks like this pull request may not have tests. Please make sure to add tests before merging. If you need an exemption to this rule, contact Hixie. Reviewers: Read the Tree Hygiene page and make sure this patch meets those guidelines before LGTMing. |
|
LGTM |
|
Build is green on the dashboard, don't know why it's reporting red here. Merging. |
Adapting changes to plugin template from: flutter/flutter#44324
Description
swift_versionsin Swift plugin podspec to make new Swift plugins work with CocoaPods in Objective-C apps.__has_includefor Swift bridging header to make new Swift plugins buildable as libraries.See lots of details in #25676 (comment) and the Swift Plugins design doc.
This does not include any migration logic needed for existing Swift plugins to adopt.
Related Issues
Fixes #25676... kind of. It fixes for NEW plugins, not existing ones.
Confirmed apps build and run on real devices and simulators running iOS 11 and iOS 13.
Tests
Checklist
///).flutter analyze --flutter-repo) does not report any problems on my PR.Breaking Change