Ivan FB 98d005c9e1

feat: consume the vendor's generated FFI bindings in waku-sys ...

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>

2026-07-16 00:56:16 +02:00

..

cmd.c

Tic tac toe example (#104)

2024-11-28 10:35:41 +01:00

lib.rs

feat: consume the vendor's generated FFI bindings in waku-sys

2026-07-16 00:56:16 +02:00