Swift Package Manager Support: Add FlutterFramework Dependency

Open Beginner friendly
  • Is something wrong?
#176 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
78/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Tech stack
flutter, swift
Domain
build-system, mobile-dev

Research direction

Find each plugin Package.swift file and the pubspec.yaml. Read the linked Flutter migration guide to confirm the dependency and minimum version requirements, then update those files accordingly. Done when every package manifest includes FlutterFramework and pubspec.yaml requires Flutter 3.41 or newer.

Written by the indexing model from the issue text.

Description

Hello,

Thank you for adding Swift Package Manager support to your plugin! Please also add the FlutterFramework dependency, as described in the updated migration guide. Future versions of Flutter will require this dependency.

  1. Add FlutterFramework to each of your plugin's Package.swift files:
    dependencies: [
+       .package(name: "FlutterFramework", path: "../FlutterFramework")
    ],
    targets: [
        .target(
            name: "plugin_name",
            dependencies: [
+               .product(name: "FlutterFramework", package: "FlutterFramework")
            ]
        )
    ]

  1. Raise your plugin's minimum Flutter version to at least 3.41 in pubspec.yaml:

    environment:
  sdk: ^3.11.0
  flutter: ">=3.41.0"

If you have questions, reach out in the #hackers-ios channel on Flutter's Discord or open a GitHub issue.

Thank you for your wonderful contributions to the Flutter ecosystem!

Dominant language
C
Stars
182
Forks
122
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from sk3llo/ffmpeg_kit_flutter

All issues in sk3llo/ffmpeg_kit_flutter

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.