rust-ffi

To generate Rust bindings from C headers, you use the bindgen tool to automatically parse C header files and create Rust FFI declarations. This allows your Rust application to directly call C functions and access C types safely.

The best way to expose Rust functions to C is by using cbindgen to automatically generate C header files from your Rust code. This defines the C-compatible API signatures required for C consumers to link against and call your Rust library.

You link a C library in Rust by configuring a build.rs script to locate and link the system or vendor library. This ensures the compiler resolves the external C symbols during the build process for your sys crate.

Yes, you can create safe Rust wrappers over unsafe FFI calls by encapsulating the raw pointer operations and C function invocations within safe Rust abstractions. This prevents memory unsafety and undefined behavior from leaking into the broader Rust application.

You need to structure a sys crate when integrating an external C library into Rust to separate the unsafe FFI bindings from the safe wrapper API. This isolates the raw C interface and handles the library linking configuration.