| commit | 939d5b40ef9559ded6829cdccc006f1c32b4582f | [log] [tgz] |
|---|---|---|
| author | Liam Appelbe <liama@google.com> | Fri Mar 07 15:19:50 2025 +1100 |
| committer | Liam Appelbe <liama@google.com> | Fri Mar 07 15:19:50 2025 +1100 |
| tree | 9a7ec0fe569ce20294e95bb5516bd38d243323df | |
| parent | fce700623f9e1031385fa9521a747d86fca30bb9 [diff] |
wip
This repository is home to Dart packages related to FFI and native assets building and bundling.
| Package | Description | Issues | Version |
|---|---|---|---|
| ffi | Utilities for working with Foreign Function Interface (FFI) code. | ||
| ffigen | Generator for FFI bindings, using LibClang to parse C, Objective-C, and Swift files. | ||
| jni | A library to access JNI from Dart and Flutter that acts as a support library for package:jnigen. | ||
| jnigen | A Dart bindings generator for Java and Kotlin that uses JNI under the hood to interop with Java virtual machine. | ||
| native_assets_builder | This package is the backend that invokes build hooks. | ||
| native_assets_cli | A library that contains the argument and file formats for implementing a native assets CLI. | ||
| native_toolchain_c | A library to invoke the native C compiler installed on the host machine. | ||
| objective_c | A library to access Objective C from Flutter that acts as a support library for package:ffigen. | ||
| swift2objc | A tool for generating bindings that allow interop between Dart and Swift code. | ||
| swiftgen | A tool for generating bindings that allow interop between Dart and Swift code. |
Packages not on this repo but also related to FFI and native assets. ❤️
| Package | Description | Version |
|---|---|---|
| native_toolchain_go | A library to invoke the native Go compiler installed on the host machine. | |
| native_toolchain_rust | A library to invoke the native Rust compiler installed on the host machine. |
For information about our publishing automation and release process, see https://github.com/dart-lang/ecosystem/wiki/Publishing-automation.
For additional information about contributing, see our contributing page.