-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Uncaught Error: Module did not self-register. #11
Comments
If AppVeyor is to blame, please tell them in the discussion: http://help.appveyor.com/discussions/problems/2667-iojs-not-loading-binding |
sorry i'm not sure about what exactly course the error.
the call stack should goto |
My error points to line 2 of one of my files. That line looks like this: var fswin = require("fswin"); Can you try testing with AppVeyor? It'd probably be a good idea as it's the free Windows-based CI that the Node/IO community uses. |
This could be a exposing an fswin issue with other Windows-based environments. |
You should not use the node executable when building with io.js, if you do, the native module needs to be built with the win_delay_load_hook (https://github.com/TooTallNate/node-gyp/blob/master/addon.gypi#L4) set to true. See nodejs/node#751 Here is one way to use appveyor without that error: https://github.com/nodejs/nan/blob/master/appveyor.yml#L32 You check the version first, and then you call the correct binary afterwards. |
@JCMais thanks! You might find this informative: http://help.appveyor.com/discussions/problems/2667-iojs-not-loading-binding#comment_37684231 |
https://ci.appveyor.com/project/stevenvachon/winattr/build/job/93nr8xhqxqvamlw7
The text was updated successfully, but these errors were encountered: