Hi Ze,

I haven't heard of anyone porting Cap'n Proto to QNX, but it should be
possible.

`sigaltstack()` is only used as part of `printStackTraceOnCrash()`, which
is a totally optional helper that is very OS-specific. You could start by
adding some #if/#else such that this function is empty on QNX. There's
probably a number of other places around the library where you'll need to
do similar things, but not too many, as long as you're sticking to just
libkj and libcapnp. libkj-async will probably be a lot more complicated to
support, but it's only needed for RPC -- if you only care about
serialization then you can ignore that part.

-Kenton

On Wed, Dec 7, 2022 at 12:51 AM Ze Liu <[email protected]> wrote:

> Hi everyone,
>
> Recently I'm working on building capnp libraries on QNX. And I faced an
> issue that kj library source code has the same header files with QNX, like
> ‘exception.h’. And also the kj library needs some interfaces that QNX
> doesn't provide, like signaltstack. For this interface, the QNX header file
> says not supported for now.
>
> I wonder is there a special version adapted with QNX? Or has anyone tried
> to use capnp on QNX?
>
> Many thanks!
>
> --
> You received this message because you are subscribed to the Google Groups
> "Cap'n Proto" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/capnproto/1ea370eb-d111-402c-9fa8-81511c2ae7b4n%40googlegroups.com
> <https://groups.google.com/d/msgid/capnproto/1ea370eb-d111-402c-9fa8-81511c2ae7b4n%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"Cap'n Proto" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/capnproto/CAJouXQkmxbJrYOpk4_6XAeuPrQsT4b%3D5X3CpGPuLyRZPfCjoGQ%40mail.gmail.com.

Reply via email to