Ecosyste.ms: Awesome

An open API service indexing awesome lists of open source software.

Awesome Lists | Featured Topics | Projects

https://github.com/brickpop/flutter-rust-ffi

Starter project for Flutter plugins willing to access native and synchronous rust code using FFI
https://github.com/brickpop/flutter-rust-ffi

flutter mobile native rust

Last synced: 9 days ago
JSON representation

Starter project for Flutter plugins willing to access native and synchronous rust code using FFI

Awesome Lists containing this project

README 

        
# Flutter Rust FFI Template



This project is a Flutter Plugin template. 



It provides out-of-the box support for cross-compiling native Rust code for all available iOS and Android architectures and call it from plain Dart using [Foreign Function Interface](https://en.wikipedia.org/wiki/Foreign_function_interface).



This template provides first class FFI support, **the clean way**. 

- No Swift/Kotlin wrappers

- No message passing

- No async/await on Dart

- Write once, use everywhere

- No garbage collection

- Mostly automated development

- No need to export `aar` bundles or `.framework`'s



## Getting started



### Write your native code



Edit your code within `rust/src/lib.rs` and add any dependencies you need.



Make sure to annotate your exported functions with `#[no_mangle]` and `pub extern` so the function names can be matched from Dart.



Returning strings or structs may require using `unsafe` blocks. Returned strings or structs will need to be `free`'d from Dart.



### Compile the library



- Make sure that the Android NDK is installed

  - You might also need LLVM from the SDK manager

- Ensure that the env variable `$ANDROID_NDK_HOME` points to the NDK base folder

  - It may look like `/Users/brickpop/Library/Android/sdk/ndk-bundle` on MacOS

  - And look like `/home/brickpop/dev/android/ndk-bundle` on Linux

- On the `rust` folder:

  - Run `make` to see the available actions

  - Run `make init` to install the Rust targets

  - Run `make all` to build the libraries and the `.h` file

- Update the name of your library in `Cargo.toml`

  - You'll need to update the symlinks to target the new file names. See iOS and Android below.



Generated artifacts:

- Android libraries

  - `target/aarch64-linux-android/release/libexample.so`

  - `target/armv7-linux-androideabi/release/libexample.so`

  - `target/i686-linux-android/release/libexample.so`

  - `target/x86_64-linux-android/release/libexample.so`

- iOS library

  - `target/universal/release/libexample.a`

- Bindings header

  - `target/bindings.h`



### Reference the shared objects



#### iOS



Ensure that `ios/mylib.podspec` includes the following directives:



```diff

...

   s.source           = { :path => '.' }

+  s.public_header_files = 'Classes**/*.h'

   s.source_files = 'Classes/**/*'

+  s.static_framework = true

+  s.vendored_libraries = "**/*.a"

   s.dependency 'Flutter'

   s.platform = :ios, '8.0'

...

```



On `flutter/ios`, place a symbolic link to the `libexample.a` file



```sh

$ cd flutter/ios

$ ln -s ../rust/target/universal/release/libexample.a .

```



Append the generated function signatures from `rust/target/bindings.h` into `flutter/ios/Classes/MylibPlugin.h`



```sh 

$ cd flutter/ios

$ cat ../rust/target/bindings.h >> Classes/MylibPlugin.h

```



In our case, it will append `char *rust_greeting(const char *to);` and `void rust_cstr_free(char *s);`



NOTE: By default, XCode will skip bundling the `libexample.a` library if it detects that it is not being used. To force its inclusion, add dummy invocations in `SwiftMylibPlugin.swift` that use every single native function that you use from Flutter:



```kotlin

...

  public func dummyMethodToEnforceBundling() {

    rust_greeting("...");

    compress_jpeg_file("...");

    compress_png_file("...");

    // ...

    // This code will force the bundler to use these functions, but will never be called

  }

}

```



If you won't be using Flutter channels, the rest of methods can be left empty.



> Note: Support for avmv7, armv7s and i386 is deprecated. The targets can still be compiled with Rust 1.41 or earlier and by uncommenting the `make init` line on `rust/makefile`



#### Android



Similarly as we did on iOS with `libexample.a`, create symlinks pointing to the binary libraries on `rust/target`.



You should have the following structure on `flutter/android` for each architecture:



```

src

└── main

    └── jniLibs

        ├── arm64-v8a

        │   └── libexample.so@ -> ../../../../../rust/target/aarch64-linux-android/release/libexample.so

        ├── armeabi-v7a

        │   └── libexample.so@ -> ../../../../../rust/target/armv7-linux-androideabi/release/libexample.so

        ├── x86

        │   └── libexample.so@ -> ../../../../../rust/target/i686-linux-android/release/libexample.so

        └── x86_64

            └── libexample.so@ -> ../../../../../rust/target/x86_64-linux-android/release/libexample.so

```



As before, if you are not using Flutter channels, the methods within `android/src/main/kotlin/org/mylib/mylib/MylibPlugin.kt` can be left empty.



### Exposing a Dart API to use the bindings



To invoke the native code: load the library, locate the symbols and `typedef` the Dart functions. You can automate this process from `rust/target/bindings.h` or do it manually.



#### Automatic binding generation



To use [ffigen](https://pub.dev/packages/ffigen), add the dependency in `pubspec.yaml`.



```diff

 dev_dependencies:

   flutter_test:

     sdk: flutter

+  ffigen: ^1.2.0

```



Also, add the following lines at the end of `pubspec.yaml`:



```yaml

ffigen:

  output: lib/bindings.dart

  headers:

    entry-points:

    - rust/target/bindings.h

  name: GreeterBindings

  description: Dart bindings to call mylib functions

```



**On MacOS**:

```sh

brew install llvm

flutter pub run ffigen:setup -I/usr/local/opt/llvm/include -L/usr/local/opt/llvm/lib

```



**On Linux**:

```sh

sudo apt-get install -y clang libclang-dev

flutter pub run ffigen:setup

```



Generate `lib/bindings.dart`:

```sh

flutter pub run ffigen

```



Finally, use the generated `GreetingBindings` class. An example wrapper [is available here](./lib/mylib.dart).



#### Manual bindings



Load the library: 

```dart

final DynamicLibrary nativeExampleLib = Platform.isAndroid

    ? DynamicLibrary.open("libexample.so")   // Load the dynamic library on Android

    : DynamicLibrary.process();              // Load the static library on iOS

```



Find the symbols we want to use, with the appropriate Dart signatures:

```dart

final Pointer Function(Pointer) rustGreeting = nativeExampleLib

    .lookup Function(Pointer)>>("rust_greeting")

    .asFunction();



final void Function(Pointer) freeGreeting = nativeExampleLib

    .lookup)>>("rust_cstr_free")

    .asFunction();

```



Call them:

```dart

// Prepare the parameters

final name = "John Smith";

final Pointer namePtr = Utf8.toUtf8(name);

print("- Calling rust_greeting with argument:  $namePtr");



// Call rust_greeting

final Pointer resultPtr = rustGreeting(namePtr);

print("- Result pointer:  $resultPtr");



final String greetingStr = Utf8.fromUtf8(resultPtr);

print("- Response string:  $greetingStr");

```



When we are done using `greetingStr`, tell Rust to free it, since the Rust implementation kept it alive for us to use it.

```dart

freeGreeting(resultPtr);

```



## More information

- https://dart.dev/guides/libraries/c-interop

- https://flutter.dev/docs/development/platform-integration/c-interop

- https://github.com/dart-lang/samples/blob/master/ffi/structs/structs.dart

- https://mozilla.github.io/firefox-browser-architecture/experiments/2017-09-06-rust-on-ios.html

- https://mozilla.github.io/firefox-browser-architecture/experiments/2017-09-21-rust-on-android.html