#dylib #dlopen #define


Easy to use, simple, stable ABI for Rust-libraries. Allows creating dynamically loadable plugins written in rust.

18 releases

0.17.6 Jul 2, 2024
0.17.5 Jul 2, 2024
0.17.4 May 12, 2024
0.17.0-beta.15 Apr 30, 2024

#122 in FFI

Download history 291/week @ 2024-04-04 378/week @ 2024-04-11 151/week @ 2024-04-18 767/week @ 2024-04-25 276/week @ 2024-05-02 338/week @ 2024-05-09 18/week @ 2024-05-16 3/week @ 2024-05-23 2/week @ 2024-05-30 2/week @ 2024-06-06 3/week @ 2024-06-13 103/week @ 2024-06-27

108 downloads per month


7.5K SLoC

Welcome to Savefile-abi!

Full docs: https://docs.rs/savefile-abi/latest/

Savefile-abi is a crate that is primarily meant to help building binary plugins using Rust.

savefile-abi = "0.17"
savefile = "0.17"
savefile-derive = "0.17"


Let's say we have a crate that defines this trait for adding u32s:


use savefile_derive::savefile_abi_exportable;

pub trait AdderInterface {
    fn add(&self, x: u32, y: u32) -> u32;

Now, we want to implement addition in a different crate, compile it to a shared library (.dll or .so), and use it in the first crate (or some other crate):


use interface_crate::{AdderInterface};
use savefile_derive::savefile_abi_export;

struct MyAdder { }

impl AdderInterface for MyAdder {
    fn add(&self, x: u32, y: u32) -> u32 {
        x + y

// Export this implementation as the default-implementation for
// the interface 'AdderInterface', for the current library.
savefile_abi_export!(MyAdder, AdderInterface);

We add the following to Cargo.toml in our implementation crate:

crate-type = ["cdylib"]

Now, in our application, we add a dependency to interface_crate, but not to ImplementationCrate.

We then load the implementation dynamically at runtime:


use savefile_abi::{AbiConnection};
use interface_crate::{AdderInterface};

fn main() {
    // Load the implementation of `dyn AdderInterface` that was published
    // using the `savefile_abi_export!` above.
    let connection = AbiConnection::<dyn AdderInterface>

    // The type `AbiConnection::<dyn AdderInterface>` implements
    // the `AdderInterface`-trait, so we can use it to call its methods.
    assert_eq!(connection.add(1, 2), 3);


There are multiple limitations:

  • Tuples are presently not supported as direct function arguments!
  • There may be safety issues, Savefile-Abi is not mature yet.

See full docs: https://docs.rs/savefile-abi/latest/


~71K SLoC