#cbindgen — Public Fediverse posts

And there is #cbindgen which is designed to somehow support my use case (calling Rust code from C) but it generates the C header instead of relying on existing ones.

So far I guess the way to go is to use bindgen to generate the bindings and manully adapt the generated code by replacing `extern { fn foo(); }` with `#[no_mangle] pub extern fn foo() { ... }`.

Am I missing something?

There is also a blog post by Lars Bergstrom: https://security.googleblog.com/2024/02/improving-interoperability-between-rust-and-c.html There Lars mentions some of the cool #Rust crates that we've contributed to: #cxx, #autocxx, #bindgen, #cbindgen, #diplomat, and #crubit. Some of these projects are from #Google, others are open source projects that we use and contribute to.

There is also a blog post by Lars Bergstrom: https://security.googleblog.com/2024/02/improving-interoperability-between-rust-and-c.html There Lars mentions some of the cool #Rust crates that we've contributed to: #cxx, #autocxx, #bindgen, #cbindgen, #diplomat, and #crubit. Some of these projects are from #Google, others are open source projects that we use and contribute to.