3 ms·
Much like the other Beej guides, the target isn't that tightly constrained. This aims at POSIX options, and attempts to cover gotchas for cross-platform code.
by syntheticnature 3y ago
Much like the other Beej guides, the target isn't that tightly constrained. This aims at POSIX options, and attempts to cover gotchas for cross-platform code.
Not to mention that just because you're only developing for Linux doesn't guarantee you'll have Binder or D-Bus.
- charcircuit 3y ago>the target isn't that tightly constrained Yes, which is why I highlighted that it is incomplete if you are not limiting yourself to just POSIX. It's important for readers to understand the scope of what is contained in the guide as it would be easy to think this is all the IPC mechanisms Linux offers. >developing for Linux doesn't guarantee you'll have Binder or D-Bus This is technically true, but everywhere Linux is used will likely already have one of them: embedded, mobile, desktop, server, etc. For D-Bus you can even have it work in a peer to peer mode where you don't need the daemon.
- teunispeters 3y agoNeither are present in OpenWRT family, for instance. OpenWRT has developed "ubus" as kind of a dbus-alternative, but it's definitely complicated to work with effectively. Classic (Beej style) IPC though works fine.
- syntheticnature 3y agoAs someone who has done quite a bit of embedded Linux development, I assure you: neither is as common as you think.