Hi Laurie, If you only need the serialization bits you should be able to avoid the platform specific stuff. I don't think there is a definitive list of platform specific calls for the C++ lib. These are restricted to networking and concurrency AFAIK. So for serialization you should be able to build a custom lib or just compile the serialization stuff into your module. I have done something similar on occasion.
If you are handling the UDP you can use TMemoryBuffer (in TBufferTransports.h/.cpp) as your end point transport and layer your protocol of choice on top (e.g. TCompactProtocol.h/.tcc, TBinaryProtocol.h/.tcc). You may need to compile in another .cpp or two but other than that I think you should be clear of platform lock in with a basic serialization stack. Best, Randy On Thu, Jun 19, 2014 at 7:12 AM, Laurie Bax (JIRA) <j...@apache.org> wrote: > Laurie Bax created THRIFT-2583: > ---------------------------------- > > Summary: Thrift on xPC target (SpeedGoat) > Key: THRIFT-2583 > URL: https://issues.apache.org/jira/browse/THRIFT-2583 > Project: Thrift > Issue Type: Question > Components: C++ - Library > Environment: xPC Target (SpeedGoat) real-time platform from MathWorks > Reporter: Laurie Bax > > > Has anyone attempted to compile thrift for an xPC target platform? I want to > use thrift to handle serialization and deserialization of UDP packets on such > platform. However, it seems (on windows) thrift uses some Windows-only > libraries (like WS2_32.dll). Is there a way to circumvent this? Or is there a > list of system dependent functions thrift needs? > > Thank you. > > > > -- > This message was sent by Atlassian JIRA > (v6.2#6252)
