While it's theorically possible to bypass node-gyp, I'm not aware of any actively used method that would do so. The node-gyp is a bundled dependency of npm, and is the code that parses the native module information (the bindings.gyp file that is), in order to generate the Makefile that will build the module. This Makefile will contain all the appropriate hard-coded information pertaining to the version of the runtime this module needs to be build against, including the path to the openssl headers that node-gyp just downloaded for the runtime in its local cache folder.
On Fri, Aug 3, 2018, 20:01 Steve Langasek <steve.langa...@canonical.com> wrote: > Nicolas, thanks for the clarification. Just to be sure, is node-gyp the > *only* way to build binary add-ons for node, or is it possible that some > users have built add-ons using some other build system? > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1779863 > > Title: > Ubuntu nodejs package isn't ABI compatible with mainline nodejs. > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/nodejs/+bug/1779863/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1779863 Title: Ubuntu nodejs package isn't ABI compatible with mainline nodejs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nodejs/+bug/1779863/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs