SystemsGuide
Safe Rust Bindings for a C Library a Worked Example
A good binding is two crates. The sys crate mirrors the C header exactly, and the safe crate hides the pointers behind types that cannot be misused.
19 min read
Tag
ffi
4 posts
Systems
Ownership Across FFI in Rust Who Frees the Memory Explained
Memory must be freed by the allocator that created it. At an FFI boundary that means every allocation travels with a matching free function on the same side.
4 min read
SystemsGuide
Calling Rust From C With Cbindgen and Staticlib Step by Step
To expose Rust to C, mark functions extern "C" with a stable name, build a staticlib or cdylib and let cbindgen write the header. The rules are about layout, ownership and panics.
17 min read
SystemsGuide
Calling C From Rust With Extern and Bindgen Step by Step
Rust calls C through extern declarations that you write or generate. bindgen reads a header and produces them, leaving you to wrap the unsafe calls in a safe API.
17 min read