Native add-ons not working when creating Windows executable, unless the executable is named nw.exe

[theabraham]

I wrote to the mailing list about this issue: https://groups.google.com/forum/#!topic/node-webkit/tXPE_WRpW2s

I'm using two node add-ons (node-ffi and ref) that I've been able to successfully require() while running as a package .nw app. However, when I created an executable with the copy /b nw.exe+myApp.nw myApp.exe command, I get the following error on requiring the add-ons:

Uncaught Error: the specified module could not be found. 
C:\Users\Me\AppData\Local\Temp\nw6252_26230\node_modules\ref\build\Release\binding.node

What's strange, though, is that when I rename the executable from myApp.exe to nw.exe everything works (the add-ons are successfully required!)

Any ideas what's going on?

[rogerwang]

Thanks for reporting. This is duplication with #199 .

The reason is that the library files we released -- nw.lib and nw.exp refers to nw.exe.

This looks like a nature of Win DLL linking. I'll look into it at some point.