Jetson support

[jimmy1977]

Hi

I am going through the flow IPC codebase. First of all excellent work. This is exactly what I was hoping not to write on my own. I am trying to build for jetson architecture. I see a few static asserts in the code that will fail at compile time if I try to use it on a jetson system.

I am wondering if there are any work arounds or is support planned for other architectures besides x86_64.

[jimmy1977]

I am also having issues building with ubuntu20.04. Compatibility with

• boost
• libfmt

[ygoldfeld]

Hi there, @jimmy1977 - methinks I need a better notification system for when people ask questions. Granted, in any case I've been overloaded with work (though much of it is related to Flow-IPC). Nevertheless, a big, big release is coming with lots of good stuff. But I digress.

Regarding support for other architectures: see https://flow-ipc.github.io/doc/flow-ipc/versions/main/generated/html_public/about.html - some notes on that there. Moreover, there should be a topic nearby, but more importantly a ticket linked therein, about what it would take to port to macOS+ARM and Windows. That ticket is quite detailed, actually.

It's one of those things where, if I am the only one working on the project in earnest, then since it's not my current priority, it won't magically happen... but this being open-source, contributions from others are more than welcome. As noted in the placed mentioned above, it's very much doable. macOS/ARM especially.

--

As for the problems with Boost and libfmt: Naturally, I don't know what you mean (since apparently I haven't seen the same problems), but I would strongly suggest:

• (ideally) Fork the project, then in your fork add an Ubuntu20-04 config in main.yml, then run that pipeline - the errors will readily reproduce! Then either fix the problem yourself, or file a ticket, linking and/or pasting the details.
• (less ideally but still pretty good) File a ticket; show what's going wrong.

All in all, for a project written by 2 people and maintained by 1 (me!), there is quite a lot of care put into it... BUT, as it stands, things might not magically get fixed, unless I happen to be specifically working on those things... in which case, in the spirit of open source, your help would be, like, helpful. Which should in turn resolve speed up resolving your problems.