feat(macos): add Swift Package Manager support - #655
Open
zkrige wants to merge 1 commit into
Open
Conversation
Moves the single macOS source file into the SPM layout Flutter expects (macos/flutter_tts/Sources/flutter_tts/) and adds a Package.swift modelled on the Flutter team's own url_launcher_macos. The podspec now points at the same sources, so CocoaPods builds are unchanged and both mechanisms stay supported. Without this, any host app on Swift Package Manager (the default for new Flutter projects) sees 'The following plugins do not support Swift Package Manager for macos: flutter_tts' and is forced to keep CocoaPods.
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
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.
The macOS implementation has no
Package.swift, so any host app using Swift Package Manager (the default for new Flutter projects) sees:and is forced to keep CocoaPods for the whole app. Flutter warns this will become an error in a future release.
This moves the single macOS source file into the layout Flutter expects (
macos/flutter_tts/Sources/flutter_tts/) and adds aPackage.swiftmodelled on the Flutter team's ownurl_launcher_macos.The podspec now points at the same sources, so CocoaPods builds are unchanged and both mechanisms stay supported. No behaviour change.
Verified in a real app: with this branch the plugin drops off the unsupported list and the macOS build succeeds under SPM.