On Monday, January 28, 2013 1:31:23 PM UTC+2, Ben Noordhuis wrote:
>
> On Mon, Jan 28, 2013 at 9:33 AM, Zoid <andy.m...@gmail.com <javascript:>>
> wrote:
>
> Something like this should work:
>
> var foo = require('build/Release/foo.' + process.arch + '.node');
>
> Compile your module twice (or thrice, if you want to support ARM) to
> out/Release/foo.ia32.node and out/Release/foo.x64.node.
>
It's a great advice, thank you.
>
> > 2. Is there a way to help module maintainers to include precompiled
> binaries
> > in their npm packages? Are binaries still supported? I'd like to start
> with
> > ws and xxhash - they both don't have binaries included at least for x64.
> >
>
> You can ship .node files with a npm module and some modules do. See
> the bson module for an example.
>
The question was not how to ship .node files, but how to cooperate with
module maintainers. I don't want to take full responsibility to maintain
module, but can give .node files to the maintainer to include. Does anybody
already do this?
Andy
--
--
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 nodejs@googlegroups.com
To unsubscribe from this group, send email to
nodejs+unsubscr...@googlegroups.com
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, send email to
nodejs+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
