mirror of
https://github.com/logos-messaging/logos-delivery-rust-bindings.git
synced 2026-07-30 06:53:29 +00:00
98d005c9e1
nim-ffi 0.2.0 generates the Rust bindings from the Nim source, so bindgen over the hand-written headers is no longer the source of truth -- and could not be, since those headers describe the pre-CBOR ABI. The generated sources are referenced in place under vendor rather than copied, so regenerating them in logos-delivery flows straight through with nothing to keep in sync. They stay sibling modules because api.rs resolves its neighbours through `super::`. build.rs keeps driving the build: it runs the vendor's make target, scans for the version-and-hash-named nimble package dirs and librln, and emits the miniupnpc / natpmp / c++ link flags. The generated build.rs does none of that (it runs a bare `nim c --mm:orc` against a path that does not resolve here), so only the bindgen half is dropped. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Waku Rust bindings
Rust layer on top of logos-messaging-nim C FFI bindings.
About Waku
Waku is a family of robust and censorship-resistant communication protocols enabling privacy-focused messaging for Web3 applications.
Private. Secure. Runs anywhere.
Read the Waku docs