-
Notifications
You must be signed in to change notification settings - Fork 62
Install fails on Win 7 x64 with VS2010 & VS2013 (or just VS2013) #110
Comments
Also... |
👍 Waiting for a fix..
|
I don't have any experience with node + windows, but I don't think there's anything to fix in Contextify. If there's an issue, it seems like this would be a node-gyp issue. |
There is no .vcxproj file in node-gyp project as well. @brianmcd, I'm wondering where it could come from.. |
My best guess is that gyp generates that file. |
I was able to install contextify on Windows 8.x by using these steps:
|
@koistya Thanks a lot for your solution. It helped me on Windows 8.1 x64 to switch to x86 version of node. Builds don't crash anymore. In my case it was actually ws library as a dependency of socket.io, but the same error. |
@koistya the solution works great! thx! |
Hi,
When VS2013 is installed you get the following error:
LINK : fatal error LNK1181: cannot open input file 'kernel32.lib' [C:\Source\POC\ExpressApp1\node_modules\contextify\build\contextify.vcxproj]
I've identified a way to fix (well works for me) this looks to be that GYP is not generating correct project options for VS2013. To resolve you just: -
Then you can npm install your modules that are defendant on contextify.
Hope this helps.
Nick
The text was updated successfully, but these errors were encountered: