Samori, you should definitely update your example module to use node-gyp instead of node-waf! We want new module authors to use the new stuff; forward compatibility and all that.
On Tue, Feb 7, 2012 at 8:14 AM, Samori Gorse <[email protected]> wrote: > +1 on the general idea. > > I've been waiting for the node-waf -> node_gyp switch for a while now. > I'm working on a project to help node.js module authors get started with > the whole C++ thing: > > https://github.com/shinuza/node-cc-module-boilerplate > > The biggest problem with node-waf is that the version bundled with node is > super outdated and the documentation is hard to find. Same thing goes with > the automated doc for the V8 API. > > > 2. We'll build some cloudy buildbot CI stuff to compile all the things. > > I thought of this while reading the original post, although it might > require some special setup to register a particular module for compiling. > > -- > 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 >
