Novo: I'm sorry, but I have to slightly correct you Multi-process is not always the same thing as multi-executable... Actually it is much easier to create multi-process architecture by simply forking single executable - it makes the IPC and data sharing much simpler. I'm looking at my Chrome now and it uses single executable almost for everything, the only exceptions being NaCl support and sandbox (for obvious security reasons).

Also, I guess for the OPs problem it doesn't matter much if there were multiple binaries. The main idea is that the executables must be self-contained and not depend on anything outside, that could be updated by the OS.

seasoned_geek: BTW: Did you consider other ways to encapsulate your application so it can't be broken by updates? Technologies like Flatpak or Snap wrap all the dependencies of your application into single container, so it might might give you what you want, without resorting to static linking. Or you could perhaps use Docker, which provides the same or even higher level of separation, with added benefit that you could only create a single image for all the distributions you want to support.

Honza