-
Notifications
You must be signed in to change notification settings - Fork 12
Add a POSIX C LDK networking library #34
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
Conversation
... and OSX complains that "redefinition of typedef...is a C11 feature"
ec0b57e to
35c9191
Compare
|
Updated to upstream + lightningdevkit/rust-lightning#988 (which hopefully will go in 0.0.99). |
jkczyz
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Reviewed at a very high-level. Unable to run because demo.cpp needs to updated (see comment).
It appears somehow the LLVM IR is slipping into the Rust library, causing Ubunto link to fail with the following error: /usr/bin/ld: error: LLVM gold plugin has failed to create LTO module: Invalid record clang: error: linker command failed with exit code 1 (use -v to see invocation)
|
Updated to latest upstream again. |
lightning-c-bindings/Cargo.toml
Outdated
| lightning = { git = "https://github.com/rust-bitcoin/rust-lightning", rev = "865c6ba04eef70ed33afe484e9df7d12093fc598", features = ["allow_wallclock_use"] } | ||
| lightning-persister = { git = "https://github.com/rust-bitcoin/rust-lightning", rev = "865c6ba04eef70ed33afe484e9df7d12093fc598" } | ||
| lightning-invoice = { git = "https://github.com/rust-bitcoin/rust-lightning", rev = "865c6ba04eef70ed33afe484e9df7d12093fc598" } | ||
| lightning-background-processor = { git = "https://github.com/rust-bitcoin/rust-lightning", rev = "865c6ba04eef70ed33afe484e9df7d12093fc598" } |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I take it this needs to be updated for 0.0.99?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Huh! I'd intended to, but apparently set it to the wrong value. In any case I'll need to update it one more time before merge once 0.0.99 is tagged upstream, but that just changes the last commit so I won't bother with re-review.
Turns out there is no good option in swift, so we should just do it in C here.