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!
Ben Noordhuis
unread,
Oct 2, 2012, 9:30:25 AM10/2/12
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to nod...@googlegroups.com
Upvote for great good. Every module author should read it.
Tim Caswell
unread,
Oct 2, 2012, 10:22:36 AM10/2/12
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to nod...@googlegroups.com
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.