-
Notifications
You must be signed in to change notification settings - Fork 57
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: C bindings for Waku Relay #1632
Comments
Ivansete-status
added a commit
that referenced
this issue
May 4, 2023
Ivansete-status
added a commit
that referenced
this issue
May 4, 2023
2 tasks
Ivansete-status
added a commit
that referenced
this issue
May 12, 2023
* feat(cbindings): first commit - waku relay (#1632) * test_app.nim: fix compilation issue. App.init(..) -> App.new(..) * Simplifying library name (libwaku) and standardizing function names (waku_*) * Proper wrapper of the waku_node API and creation of the libwaku.a * Rolling back changes that are not needed * Rolling back changes that are out of the scope of this task * wakunode.nim: Removing unnecessary import * Aplying PR suggestions * Renaming 'waku.h' -> 'libwaku.h' * Use of 'isNil' instead of '== nil' * libwaku.nim: explicitly setting waku_poll() as gcsafe
3 tasks
This was referenced Jun 12, 2023
3 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Problem
nwaku can't be easily exported to other environments, such as NodeJS or Rust.
Suggested solution
Have nwaku C bindings so that a NodeJS user can easily start a Waku node in Relay mode.
Additional context
This is a first step of having a full operative Waku node in other platforms. For now we focus on the Waku Relay protocol.
We want to tackle the nwaku C-bindings option of: "use nwaku with NodeJS" - #1332
The final goal that we chase: "C-bindings for Kotlin, Rust, etc" - #904
Acceptance criteria
The text was updated successfully, but these errors were encountered: