Native addon's are dynamically linked to nw.exe

[justinmchase]

I thought it was linking to nw.lib, why does it have a dynamic link to nw.exe also? I don't want to actually call any of the nw api's from native code, just normal v8 bindings. Is there a way to avoid the nx.exe dependency?

[justinmchase]

Actually, I think I understand why this is the way it is. It threw me off a bit because it's being loaded by nw.exe but of course nw is dynamically loading it so it would need to have the reverse dependency for this to make sense.

I'm going to file an issue with the nw project but just in case someone here has a recommendation I am encountering two issues I'm not sure how to resovle with this:

• Renaming nw.exe to app.exe causes it to fail to load my native modules
• I am unable to load my native modules in iojs.exe for testing

Funny enough, if I compile using node-gyp instead of nw-gyp, then just rename nw.exe to iojs.exe then my module will run in both environments. So I'm trying to figure out the cleanest way to handle this situation.