-
Notifications
You must be signed in to change notification settings - Fork 27.9k
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
☂️ Add Swift Package Manager compatibility #126005
Comments
This comment was marked as off-topic.
This comment was marked as off-topic.
Would be nice to support spm for linux, windows and android targets too. |
@renanyoy Flutter does not support Swift as a language for any of those platforms. If you want to propose new supported languages that would need to be a new issue. |
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
@stuartmorgan , I have opened a new issue to handle it #139563 |
This is exciting work. Please consider in the migration path that SPM will ignore architecture exclusions when a scheme includes "debug" or "development" in its name. Flutter requires "Debug" as a prefix. |
Flutter iOS/macOS is migrating to Swift Package Manager for native dependencies. This is an experimental feature this isn't ready yet for app developers. However, plugin authors should add Swift Package Manager support to their packages. The faster plugin authors add SwiftPM support, the sooner we can drop CocoaPods (and make it easier to install Flutter iOS!). There's [~10K Flutter iOS plugins](https://gist.github.com/loic-sharma/891a358f8abab36133e8a9395f719296) that'll need to migrate, so we really need the plugin migration docs to be as easy to follow as possible. Any and all feedback is appreciated! :) This is based off @vashworth's [guide](flutter/flutter#146256 (comment)). Question for reviewers: What do you think of the doc structure? Should we rearrange things to make it clearer that some sections are to be followed when things go wrong? Or is the current structure clear enough? Preview URLs: 1. [Swift Package Manager for app developers](https://flutter-docs-prod--pr10827-spm-compatibility-ilxd3b00.web.app/packages-and-plugins/swift-package-manager/for-app-developers) 2. [Swift Package Manager for plugin authors ](https://flutter-docs-prod--pr10827-spm-compatibility-ilxd3b00.web.app/packages-and-plugins/swift-package-manager/for-plugin-authors) Part of flutter/flutter#126005 ## Presubmit checklist - [ ] This PR is marked as draft with an explanation if not meant to land until a future stable release. - [x] This PR doesn’t contain automatically generated corrections (Grammarly or similar). - [x] This PR follows the [Google Developer Documentation Style Guidelines](https://developers.google.com/style) — for example, it doesn’t use _i.e._ or _e.g._, and it avoids _I_ and _we_ (first person). - [x] This PR uses [semantic line breaks](https://github.com/dart-lang/site-shared/blob/main/doc/writing-for-dart-and-flutter-websites.md#semantic-line-breaks) of 80 characters or fewer.
Updates from @orta of the CocoaPods team:
Sources: |
Work items
Add Swift Package Manager compatibility
.build
directory #148018Package.swift
file #153448SWIFT_PACKAGE_MANAGER
environment variable toFLUTTER_SWIFT_PACKAGE_MANAGER
#159121plugin_lint_mac
test for Swift Package Managerbuild_ios_framework_module_test
test for Swift Package Managerflutter build ios-framework
works as expected on non-modules if SwiftPM is enabledflutter <build> <ios>
regenerates plugins multiple times? #157391Website docs:
Additional features:
Migrate plugins to Swift Package Manager
flutter-insiders@
to try out the migration docsOS plugin authors: Consider upgrading your iOS plugins to also support Swift Package Manager
flutter create -t plugin
to recommend supporting both CocoaPods and Swift Package Manager #149855.modulemaps
(see Remove use of modulemaps in flutter/packages when using SwiftPM #148572 (comment))pod
installation, use bundled version #40135macOS
Package.swift
minimum supported platform version. Unblocks migrating:google_sign_in_ios
flutter build macos-framework
website#7225Bugs
--cocoapods
flag does not work #144244ObjcOptions.headerIncludePath
not used #147587!.gitkeep
in.gitignore
)Resources
Design doc: flutter.dev/go/swift-package-manager-plugins-v2
Original Github Issue: #33850
The text was updated successfully, but these errors were encountered: