aa36db1d29
Support for FFI calls with `@Native external` functions through Native assets on MacOS and iOS. This enables bundling native code without any build-system boilerplate code. For more info see: * https://github.com/flutter/flutter/issues/129757 ### Implementation details for MacOS and iOS. Dylibs are bundled by (1) making them fat binaries if multiple architectures are targeted, (2) code signing these, and (3) copying them to the frameworks folder. These steps are done manual rather than via CocoaPods. CocoaPods would have done the same steps, but (a) needs the dylibs to be there before the `xcodebuild` invocation (we could trick it, by having a minimal dylib in the place and replace it during the build process, that works), and (b) can't deal with having no dylibs to be bundled (we'd have to bundle a dummy dylib or include some dummy C code in the build file). The dylibs are build as a new target inside flutter assemble, as that is the moment we know what build-mode and architecture to target. The mapping from asset id to dylib-path is passed in to every kernel compilation path. The interesting case is hot-restart where the initial kernel file is compiled by the "inner" flutter assemble, while after hot restart the "outer" flutter run compiled kernel file is pushed to the device. Both kernel files need to contain the mapping. The "inner" flutter assemble gets its mapping from the NativeAssets target which builds the native assets. The "outer" flutter run get its mapping from a dry-run invocation. Since this hot restart can be used for multiple target devices (`flutter run -d all`) it contains the mapping for all known targets. ### Example vs template The PR includes a new template that uses the new native assets in a package and has an app importing that. Separate discussion in: https://github.com/flutter/flutter/issues/131209. ### Tests This PR adds new tests to cover the various use cases. * dev/devicelab/bin/tasks/native_assets_ios.dart * Runs an example app with native assets in all build modes, doing hot reload and hot restart in debug mode. * dev/devicelab/bin/tasks/native_assets_ios_simulator.dart * Runs an example app with native assets, doing hot reload and hot restart. * packages/flutter_tools/test/integration.shard/native_assets_test.dart * Runs (incl hot reload/hot restart), builds, builds frameworks for iOS, MacOS and flutter-tester. * packages/flutter_tools/test/general.shard/build_system/targets/native_assets_test.dart * Unit tests the new Target in the backend. * packages/flutter_tools/test/general.shard/ios/native_assets_test.dart * packages/flutter_tools/test/general.shard/macos/native_assets_test.dart * Unit tests the native assets being packaged on a iOS/MacOS build. It also extends various existing tests: * dev/devicelab/bin/tasks/module_test_ios.dart * Exercises the add2app scenario. * packages/flutter_tools/test/general.shard/features_test.dart * Unit test the new feature flag. |
||
|---|---|---|
| .. | ||
| android | ||
| common | ||
| ios | ||
| README.md | ||
Templates for Flutter Module
common
Written to root of Flutter application.
Adds Dart project files including pubspec.yaml.
android
library
Written to the .android/ hidden folder.
Contents wraps Flutter/Dart code as a Gradle project that defines an Android library.
Executing ./gradlew flutter:assembleDebug in that folder produces
a .aar archive.
Android host apps can set up a dependency to this project to consume Flutter views.
gradle
Written to .android/ or android/.
Mixin for adding Gradle boilerplate to Android projects.
host_app_common
Written to either .android/ or android/.
Contents define a single-Activity, single-View Android host app
with a dependency on the .android/Flutter library.
Executing ./gradlew app:assembleDebug in the target folder produces
an .apk archive.
Used with either android_host_ephemeral or android_host_editable.
host_app_ephemeral
Written to .android/ on top of android_host_common.
Combined contents define an ephemeral (hidden, auto-generated,
under Flutter tooling control) Android host app with a dependency on the
.android/Flutter library.
host_app_editable
Written to android/ on top of android_host_common.
Combined contents define an editable (visible, one-time generated,
under app author control) Android host app with a dependency on the
.android/Flutter library.
ios
library
Written to the .ios/Flutter hidden folder.
Contents wraps Flutter/Dart code for consumption by an Xcode project.
iOS host apps can set up a dependency to this contents to consume Flutter views.
host_app_ephemeral
Written to .ios/ outside the Flutter/ sub-folder.
Combined contents define an ephemeral (hidden, auto-generated,
under Flutter tooling control) iOS host app with a dependency on the
.ios/Flutter folder contents.
The host app does not make use of CocoaPods, and is therefore suitable only when the Flutter part declares no plugin dependencies.
host_app_ephemeral_cocoapods
Written to .ios/ on top of host_app_ephemeral.
Adds CocoaPods support.
Combined contents define an ephemeral host app suitable for when the Flutter part declares plugin dependencies.