CAPI is one of the names used to refer to Microsoft's old CryptoAPI library, so I would avoid that considering what I work on.
-
-
-
Good point. Considering c_bindings.rs as an alternative now.
End of conversation
New conversation -
-
-
http://ffi.rs , since the bindings are not for any specific language
-
The thing about http://ffi.rs is that it’s often used for bindings to *other* libraries, not for bindings to *this* library.
- 1 more reply
New conversation -
-
-
bridge_to_hell.rs
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
This Tweet is unavailable.
-
-
We usually create a ffi workspace member named ${LIB}-ffi. Though are increasingly finding that it's often better to use RPC instead of FFI when possible.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
@JeffryMolanus any ideas?
-
For the RAW bindings i use libwhatever-sys then wrapping them into safe code libwhatever-rs this is mostly what I do but you can also do it in a single-sys crate and use modules to only expose the safe wrappers and hide the ffi interface
End of conversation
New conversation -
-
-
I've learned to make it into a separate crate, in which case it's just src/lib.rs.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.