On Tue, Mar 25, 2014 at 7:41 AM, Kevin Ingwersen <[email protected]>wrote:
> > - How do we offer native functionality to a user? > You surface lib functionality in JS by making it available thru C++ code which is compiled into a shared/dynamic library which the lode shell loads and automatically passes messages to. Example code is in the Readme on github. > - How do we simply compile the "module", and how is it properly used? > See the Makefile entries for math_lode.so and testglue.so. - What can we do to implement said things with NPM? AKA. how is this NPM > compatible? > - How does one deploy a module using this "binding"? > The lode shared library and the C/C++ lib in question could be wrapped in an NPM package with a dependency of lode. I haven't made an NPM package for lode yet since it's still a prototype. The IPC part, as said, is quite an interesting part, as the only real good > c++ library that offers a proper implementation is Boost - problem is, that > not everyone wants to build the whole bulk of it. So an "extratable" > implementation for other, non-nodejs-oriented, applications and libraries > would be quite interesting. > Most of what lode does is enable/manage IPC. -- -- 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 --- You received this message because you are subscribed to the Google Groups "nodejs" 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.
