mirror of
https://github.com/flutter/flutter.git
synced 2025-06-03 00:51:18 +00:00
![]() This updates the Flutter minimum iOS version from 12.0 to 13.0, adds a migrator for existing apps, and updates our own examples, tests, and benchmark apps to 13.0. A follow-up patch will drop iOS 13 `@available` checks in the embedder. This is required in order to use Swift in the embedder and not need to bundle the Swift runtime libs in every app that uses Flutter. Swift stable ABI As of March 2025, usage of iOS is well below 1%, see example public usage data here: https://telemetrydeck.com/survey/apple/iOS/majorSystemVersions/ This patch makes the following changes: 1. Updates ios_deployment_target from 12.0 to 13.0. 2. Changes templates to `IPHONEOS_DEPLOYMENT_TARGET`, `MinimumOSVersion`, and Podfile `platform :ios` to 12.0. 3. Adds migrator for Podfile part to migrate `platform :ios, '11.0'` -> `platform :ios, '12.0'` 4. Compiles with `-miphoneos-version-min=12.0` 5. Runs the migrator on all example apps and integration tests. 6. Updates examples, tests to iOS 13 deployment target It also updates `verify_exported.dart`: * iOS 13 introduces stricter separation of const and non-const global symbols. Previously, these were declared in the Mach-O `__DATA` section which may be mapped read-write, but now they're in a dedicated `__DATA_CONST` section which is mapped read-only. This adds `(__DATA_CONST,__const)` to the allowlist with the same enforcement on exported symbol naming as before. See also (ios_deployment_target): * https://github.com/flutter/buildroot/pull/808 * https://github.com/flutter/buildroot/pull/574 See also (template, migrator): * https://github.com/flutter/flutter/pull/62902 * https://github.com/flutter/flutter/pull/85174 * https://github.com/flutter/flutter/pull/101963 * https://github.com/flutter/flutter/pull/140478 Issue: https://github.com/flutter/flutter/issues/167735 ## Pre-launch Checklist - [X] I read the [Contributor Guide] and followed the process outlined there for submitting PRs. - [X] I read the [Tree Hygiene] wiki page, which explains my responsibilities. - [X] I read and followed the [Flutter Style Guide], including [Features we expect every widget to implement]. - [X] I signed the [CLA]. - [X] I listed at least one issue that this PR fixes in the description above. - [X] I updated/added relevant documentation (doc comments with `///`). - [X] I added new tests to check the change I am making, or this PR is [test-exempt]. - [X] I followed the [breaking change policy] and added [Data Driven Fixes] where supported. - [X] All existing and new tests are passing. If you need help, consider asking for advice on the #hackers-new channel on [Discord]. <!-- Links --> [Contributor Guide]: https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md#overview [Tree Hygiene]: https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md [test-exempt]: https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md#tests [Flutter Style Guide]: https://github.com/flutter/flutter/blob/main/docs/contributing/Style-guide-for-Flutter-repo.md [Features we expect every widget to implement]: https://github.com/flutter/flutter/blob/main/docs/contributing/Style-guide-for-Flutter-repo.md#features-we-expect-every-widget-to-implement [CLA]: https://cla.developers.google.com/ [flutter/tests]: https://github.com/flutter/tests [breaking change policy]: https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md#handling-breaking-changes [Discord]: https://github.com/flutter/flutter/blob/main/docs/contributing/Chat.md [Data Driven Fixes]: https://github.com/flutter/flutter/blob/main/docs/contributing/Data-driven-Fixes.md |
||
---|---|---|
.. | ||
android.tmpl | ||
ios.tmpl | ||
lib | ||
linux.tmpl | ||
macos.tmpl/Classes | ||
src.tmpl | ||
windows.tmpl | ||
ffigen.yaml.tmpl | ||
README.md.tmpl |
# {{projectName}} {{description}} ## Getting Started This project is a starting point for a Flutter [FFI plugin](https://flutter.dev/to/ffi-package), a specialized package that includes native code directly invoked with Dart FFI. ## Project structure This template uses the following structure: * `src`: Contains the native source code, and a CmakeFile.txt file for building that source code into a dynamic library. * `lib`: Contains the Dart code that defines the API of the plugin, and which calls into the native code using `dart:ffi`. * platform folders (`android`, `ios`, `windows`, etc.): Contains the build files for building and bundling the native code library with the platform application. ## Building and bundling native code The `pubspec.yaml` specifies FFI plugins as follows: ```yaml plugin: platforms: some_platform: ffiPlugin: true ``` This configuration invokes the native build for the various target platforms and bundles the binaries in Flutter applications using these FFI plugins. This can be combined with dartPluginClass, such as when FFI is used for the implementation of one platform in a federated plugin: ```yaml plugin: implements: some_other_plugin platforms: some_platform: dartPluginClass: SomeClass ffiPlugin: true ``` A plugin can have both FFI and method channels: ```yaml plugin: platforms: some_platform: pluginClass: SomeName ffiPlugin: true ``` The native build systems that are invoked by FFI (and method channel) plugins are: * For Android: Gradle, which invokes the Android NDK for native builds. * See the documentation in android/build.gradle. * For iOS and MacOS: Xcode, via CocoaPods. * See the documentation in ios/{{projectName}}.podspec. * See the documentation in macos/{{projectName}}.podspec. * For Linux and Windows: CMake. * See the documentation in linux/CMakeLists.txt. * See the documentation in windows/CMakeLists.txt. ## Binding to native code To use the native code, bindings in Dart are needed. To avoid writing these by hand, they are generated from the header file (`src/{{projectName}}.h`) by `package:ffigen`. Regenerate the bindings by running `dart run ffigen --config ffigen.yaml`. ## Invoking native code Very short-running native functions can be directly invoked from any isolate. For example, see `sum` in `lib/{{projectName}}.dart`. Longer-running functions should be invoked on a helper isolate to avoid dropping frames in Flutter applications. For example, see `sumAsync` in `lib/{{projectName}}.dart`. ## Flutter help For help getting started with Flutter, view our [online documentation](https://docs.flutter.dev), which offers tutorials, samples, guidance on mobile development, and a full API reference. {{#no_platforms}} The plugin project was generated without specifying the `--platforms` flag, so no platforms are currently supported. To add platforms, run `flutter create -t plugin_ffi --platforms <platforms> .` in this directory. You can also find a detailed instruction on how to add platforms in the `pubspec.yaml` at https://flutter.dev/to/pubspec-plugin-platforms. {{/no_platforms}}