Awesome, I appreciate it! Onto the OpenNI forums! If anybody knows otherwise I'd love to hear it so I'm not banging my head against the wall needlessly. And honestly this is great news - I'm glad it wasn't what I was afraid of - that this wasn't going to be possible in Node for some silly reason.
On Tuesday, January 8, 2013 12:05:27 AM UTC-5, Ben Noordhuis wrote: > > On Tue, Jan 8, 2013 at 5:29 AM, Benjamin Farrell > <[email protected]<javascript:>> > wrote: > > Hey everyone - I'm trying to bind Node.js to the OpenNI project > > (http://www.openni.org/). I'm coming at this having not really used > much > > C++, let alone the Node build system. > > > > Anyway - I have been able to create a custom AddOn for Node via Gyp. It > > loads the proper shared libraries compiles just fine. I can even load > the > > module - but it crashes on an exception. The exception is coming from > the > > OpenNI project - however, before I post to that group, I wanted to check > > here. > > > > The reason I wanted to check here, is that the exception comes when the > > shared libraries themselves load yet ANOTHER .so file for the device > driver. > > It seems to be failing when trying to execute and initialize that shared > > library. > > > > So my question is - is there anything in Node that prevents this > behavior? > > Perhaps some kind of sandbox, or lockout, or something that prevents > shared > > libraries from loading and executing other libraries loaded at runtime? > > > > Thanks! Again, sorry if it's a silly question - all of this C++ really > > isn't my style yet, and I'm just getting my feet wet, > > Nothing I can think of. Native add-ons are loaded with > dlopen(RTLD_LAZY) and that's it, no special processing or handling. > -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
