The operating system is Windows 10
I have a project that heavily relies on native libraries, some are based on nbind others use nan directly.
On electron 2 and 3 they all work, on electron 4 (tested 4.1.3) I can't get the nbind-based modules to load.
When I try to load nbind-based native modules they all produce an error message, either "Module did not self-register." or "The specified procedure could not be found."
I've debugged the second one and the error message from the api is "entry point not found".
Now I have a bit of an idea what's the trigger for this problem because starting with electron 4 they don't ship node.dll any more, that functionality is now apparently statically linked into electron.exe.
Still, with the same build settings I got all the non-nbind modules to load correctly so I was wondering in how far nbind might be playing into this.
The operating system is Windows 10
I have a project that heavily relies on native libraries, some are based on nbind others use nan directly.
On electron 2 and 3 they all work, on electron 4 (tested 4.1.3) I can't get the nbind-based modules to load.
When I try to load nbind-based native modules they all produce an error message, either "Module did not self-register." or "The specified procedure could not be found."
I've debugged the second one and the error message from the api is "entry point not found".
Now I have a bit of an idea what's the trigger for this problem because starting with electron 4 they don't ship node.dll any more, that functionality is now apparently statically linked into electron.exe.
Still, with the same build settings I got all the non-nbind modules to load correctly so I was wondering in how far nbind might be playing into this.