Hey Matt, Do you mean SWIG (http://www.swig.org)? I've used it before, it works well, but makes for a pretty large API footprint. I totally agree that a socket connection or HTTP interface between the two things is preferable for long term or complex use. If nothing else it makes you be deliberate about your API
Best, Rob On Thu, Sep 4, 2014 at 3:38 AM, Matt Aimonetti <[email protected]> wrote: > you can use swing but in general Ruby and C++ aren't friends. You might > want to consider bridging the two worlds differently (maybe via socket > connections) > > > On Wed, Sep 3, 2014 at 6:35 PM, Chris McCann <[email protected]> > wrote: > >> I'm working on a project that needs to interface a Rails app with some >> native C++ code. I had hoped to use FFI, but it only supports C. >> >> My research shows there are other ways to do it but I'm curious if anyone >> in the group has experience interfacing Ruby code with native code in C++. >> >> If I can get this working I'll happily give a talk at SD Ruby on it! >> >> Cheers, >> >> Chris >> >> -- >> -- >> SD Ruby mailing list >> [email protected] >> http://groups.google.com/group/sdruby >> --- >> You received this message because you are subscribed to the Google Groups >> "SD Ruby" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> For more options, visit https://groups.google.com/d/optout. >> > > -- > -- > SD Ruby mailing list > [email protected] > http://groups.google.com/group/sdruby > --- > You received this message because you are subscribed to the Google Groups > "SD Ruby" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- -- SD Ruby mailing list [email protected] http://groups.google.com/group/sdruby --- You received this message because you are subscribed to the Google Groups "SD Ruby" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
