-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Parity-as-a-library #4842
Comments
...and then the ability to cross-compile this library to IOS and Android. |
Probably cross-compiling libraries containing C code... Besides that, writing C interfaces itself, cause it's super time consuming |
The C interface can be simple enough. It's mostly configuration, creating, starting and stopping Parity service and polling for status to detect critical errors. In the simplest implementation configuration can be done by passing text in toml format. So basically just 3 functions.
All other communication goes over RPC/IPC. If we want to expose our rich API to C, these bindings need to be auto-generated from RPC traits. |
That definitely seems like a good approach.
|
@debris But wouldn't that be the worry of an implementor to compile libraries that contain C code. From our side we would only need to worry about writing the C interfaces (which will take a lot of time). |
To expose the C api something like rusty-binder or rusty-cheddar would be good to use. Also, let's see if the rust team will support this in the future. |
@adrianbrink I think @debris was referring to C/C++ libraries we have as dependencies, which may be hard to cross-compile. |
Oh right. Didn't know parity had C/C++ deps. |
Reopening as I'm going to work on this soon-ish. |
The text was updated successfully, but these errors were encountered: