Replying to Avatar ChipTuner

Yes I saw, appreciate it! nostr:npub1m4ny6hjqzepn4rxknuq94c2gpqzr29ufkkw7ttcxyak7v43n6vvsajc2jl shared it too. Also appreciated!

Interop with with modern .NET (5.0 and above) just uses Platform Invoke (PInvoke) to access exported symbols in position independent shared libraries. I'm not experienced in C++, but I do remember something about symbol mangling.

So technically nothing on the C side of things, just telling the compiler to export symbols in a shared library.

Avatar
MichaelJ 1y ago

Thanks for the info!

I'm going to be deep in the weeds of C++ interop pretty soon. I've already peeked at the options, and they look interesting.

For Python, maybe C#, and some other languages, it may be as simple as exporting symbols so other languages can invoke the compiled binary.

For other languages or environments, I've been looking into gRPC, either with inter-process communication (IPC) or as a client-server connection over HTTP. Theoretically, a really lightweight client could use a remote server running NostrSDK with gRPC as a BFF for interacting with Nostr relays. I'm excited to dig into those possibilities!

Reply to this note

Please Login to reply.

Discussion

Avatar
ChipTuner 1y ago

I haven't farted much with C/nodejs interop, but I do believe that is a fairly simple option as well.