Linked is a blog article I've written about converting C libraries to use
gyp. If you have a native module that dynamically links to some external
library, then you should definitely give it a read. So far I've applied
this method to node-ffi (libffi), node-lame (libmp3lame) and node-expat
(libexpat, still awaiting Pull Request merge from @astro), and it works
great. Cheers!
> Linked is a blog article I've written about converting C libraries to use
> gyp. If you have a native module that dynamically links to some external
> library, then you should definitely give it a read. So far I've applied this
> method to node-ffi (libffi), node-lame (libmp3lame) and node-expat
> (libexpat, still awaiting Pull Request merge from @astro), and it works
> great. Cheers!
Upvote for great good. Every module author should read it.
Sounds great, except I've been having trouble using gyp to
cross-compile. Is cross-compiling something that gyp supports. In
particular I want to compile for various arm variants and the mips
that's often found in routers.
I'd love to convert all my dependencies to using gyp, but if I can't
then cross-compile it will have been a waste of time when I need that.
Great work on the article! Sorry for hijacking the thread. It just
made me think of it.
On Tue, Oct 2, 2012 at 8:30 AM, Ben Noordhuis <i...@bnoordhuis.nl> wrote:
> On Tue, Oct 2, 2012 at 6:13 AM, Nathan Rajlich <nat...@tootallnate.net> wrote:
>> Calling all native module authors!
>> Linked is a blog article I've written about converting C libraries to use
>> gyp. If you have a native module that dynamically links to some external
>> library, then you should definitely give it a read. So far I've applied this
>> method to node-ffi (libffi), node-lame (libmp3lame) and node-expat
>> (libexpat, still awaiting Pull Request merge from @astro), and it works
>> great. Cheers!
> Upvote for great good. Every module author should read it.
On Tue, Oct 2, 2012 at 7:22 AM, Tim Caswell <t...@creationix.com> wrote:
> Sounds great, except I've been having trouble using gyp to
> cross-compile. Is cross-compiling something that gyp supports. In
> particular I want to compile for various arm variants and the mips
> that's often found in routers.
> I'd love to convert all my dependencies to using gyp, but if I can't
> then cross-compile it will have been a waste of time when I need that.
> Great work on the article! Sorry for hijacking the thread. It just
> made me think of it.
> On Tue, Oct 2, 2012 at 8:30 AM, Ben Noordhuis <i...@bnoordhuis.nl> wrote:
> > On Tue, Oct 2, 2012 at 6:13 AM, Nathan Rajlich <nat...@tootallnate.net>
> wrote:
> >> Calling all native module authors!
> >> Linked is a blog article I've written about converting C libraries to
> use
> >> gyp. If you have a native module that dynamically links to some external
> >> library, then you should definitely give it a read. So far I've applied
> this
> >> method to node-ffi (libffi), node-lame (libmp3lame) and node-expat
> >> (libexpat, still awaiting Pull Request merge from @astro), and it works
> >> great. Cheers!
> > Upvote for great good. Every module author should read it.
> On Tue, Oct 2, 2012 at 7:22 AM, Tim Caswell <t...@creationix.com> wrote:
>> Sounds great, except I've been having trouble using gyp to
>> cross-compile. Is cross-compiling something that gyp supports. In
>> particular I want to compile for various arm variants and the mips
>> that's often found in routers.
>> I'd love to convert all my dependencies to using gyp, but if I can't
>> then cross-compile it will have been a waste of time when I need that.
>> Great work on the article! Sorry for hijacking the thread. It just
>> made me think of it.
>> On Tue, Oct 2, 2012 at 8:30 AM, Ben Noordhuis <i...@bnoordhuis.nl> wrote:
>> > On Tue, Oct 2, 2012 at 6:13 AM, Nathan Rajlich <nat...@tootallnate.net>
>> > wrote:
>> >> Calling all native module authors!
>> >> Linked is a blog article I've written about converting C libraries to
>> >> use
>> >> gyp. If you have a native module that dynamically links to some
>> >> external
>> >> library, then you should definitely give it a read. So far I've applied
>> >> this
>> >> method to node-ffi (libffi), node-lame (libmp3lame) and node-expat
>> >> (libexpat, still awaiting Pull Request merge from @astro), and it works
>> >> great. Cheers!
>> > Upvote for great good. Every module author should read it.
