Skip to content
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

Is there a way to make it work with Visual Studio 2015 #555

Closed
koistya opened this issue Dec 27, 2014 · 22 comments
Closed

Is there a way to make it work with Visual Studio 2015 #555

koistya opened this issue Dec 27, 2014 · 22 comments

Comments

@koistya
Copy link

koistya commented Dec 27, 2014

remote:   File "D:\Program Files (x86)\npm\1.4.28\node_modules\npm\node_modules\node-gyp\g
yp\pylib\gyp\MSVSVersion.py", line 402, in SelectVisualStudioVersion
remote:     versions = _DetectVisualStudioVersions(version_map[version], 'e' in version)
remote: KeyError: '14.0'
remote: gypnpm ERR! contextify@0.1.11 install: `node-gyp rebuild`
remote: npm ERR! Exit status 1
remote: npm ERR!
remote: npm ERR! Failed at the contextify@0.1.11 install script.
remote: npm ERR! This is most likely a problem with the contextify package,
remote: npm ERR! not with npm itself.
remote: npm ERR! Tell the author that this fails on your system:
remote: npm ERR!     node-gyp rebuild
remote: npm ERR! You can get their info via:
remote: npm ERR!     npm owner ls contextify
remote: npm ERR! There is likely additional logging output above.
remote:
remote: npm ERR! System Windows_NT 6.2.9200
remote: npm ERR! command "D:\\Program Files (x86)\\nodejs\\0.10.32\\node.exe" "D:\\Program
 Files (x86)\\npm\\1.4.28\\node_modules\\npm\\bin\\npm-cli.js" "install" "--msvs-version=14.0"
remote: npm ERR! cwd D:\home\site\wwwroot
remote: npm ERR! node -v v0.10.32
remote: npm ERR! npm -v 1.4.28
remote: npm ERR! code ELIFECYCLE
@koistya koistya changed the title Is there a way to make it work with Visual Studio 2015 (14.0) Is there a way to make it work with Visual Studio 2015 Dec 27, 2014
@springmeyer
Copy link
Contributor

To get this working we'll need to upgrade gyp to include https://code.google.com/p/gyp/source/detail?r=2013

@Globegitter
Copy link

Yep just tried with VS2015 as well - would love to see support for it.

@ru-sh
Copy link

ru-sh commented Jan 31, 2015

+1

1 similar comment
@domderen
Copy link

+1

@tonidy
Copy link

tonidy commented May 13, 2015

+1

1 similar comment
@vicentedealencar
Copy link

+1

@toddpi314
Copy link

+1 - this is blocking a few teams working on building NPM backed WUP apps for Win10

@voku
Copy link

voku commented May 19, 2015

+1

1 similar comment
@Dmitra
Copy link

Dmitra commented May 20, 2015

+1

@toddpi314
Copy link

So, it says pretty clearly in the docs that you have to have VS C++ 2012/2013 installed.
https://github.com/TooTallNate/node-gyp#installation

After doing this, I was able to build in VS2015 just fine.

@Dmitra
Copy link

Dmitra commented May 21, 2015

I experience this issue having only VS2012/13 installed
The issue appeared after removing VS2010. That was done intentionally, because older VS versions doesn't support some modern features to build https://www.npmjs.com/package/sharp

libcpmt lib missing

@TooTallNate
Copy link
Contributor

Please try node-gyp v2.0.0, which updated gyp to include MSVS 2015 support.

@Dmitra
Copy link

Dmitra commented May 29, 2015

not sure about VS2015 installed alone, but for VS2012/13 on Windows8.1 the issue remains.
As soon as nodejs installation doesn't include node-gyp 2.0.0 yet, I replaced old version with 2.0 manually. But the issue is still there.
node-gyp2

@Dmitra
Copy link

Dmitra commented May 30, 2015

thank you very much, the issue is gone with VS2015 installation

@ghost
Copy link

ghost commented Jun 6, 2015

👍
libuv is also updated to build with VS2015 in v1.6.0+
https://github.com/libuv/libuv/releases/tag/v1.6.0

@sisyfus
Copy link

sisyfus commented Aug 4, 2015

I'm trying to install the iron-meteor/iron-cli package, and I'm getting the same error as Dmitra. I think the problem might be that it's trying to use an old version of node-gyp, despite the fact that I do have V2 installed.(verified with npm list -g node-gyp). Referring to the highlighted node-gyp version in Dmitra's screen grab - it says V1.0.3 for me in my log. Any ideas why it's trying to use an older version of node-gyp?

@sisyfus
Copy link

sisyfus commented Aug 4, 2015

Fixed! I think the root cause was that I had not updated npm using the proper process for Windows. (along with node-gyp having not been updated initially)

@Mirodil
Copy link

Mirodil commented Sep 24, 2015

+1

@karimcitoh
Copy link

+1

1 similar comment
@godlzr
Copy link

godlzr commented Jul 12, 2016

+1

@ioandev
Copy link

ioandev commented Feb 10, 2017

+1, using vs 2015

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests