-
Notifications
You must be signed in to change notification settings - Fork 100
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
Not able to install DevTools Terminal on Window 7 #9
Comments
You have to install python. |
Does the version matter? I'm windows 7 as well and have just had a go with 3.3 and 2.7. |
Same! Both python versions, windows 7! |
Installed Python 3.3.3, added it to PATH so i could run the command EDIT |
I've been getting an error at the same place as anup. after a fair bit of Googling I was directed to https://github.com/TooTallNate/node-gyp#installation and recommend to install MS visual studio, as well as a 64 bit sdk. That was all and well but proved relatively fruitless. The command line did instruct me to tell the author that "this" (see below) fails on my system: I hope this is helpful. Thanks |
Disclaimer: I'm not a big Windows guru, so this maybe not the best approach. I managed to install
|
Also, since these compiler errors are being produced by pty.js library, I suggest everyone who's having problems with installing pty.js on Windows to report issues directly to pty.js maintainers: https://github.com/chjj/pty.js/issues |
Hi gelus I ran into similar problems on Win7 x64 (mongoose in my case). After digging for quite a while I found that your sdk has to be set properly first. To do this, open a command prompt and navigate to: |
When I install devtools-terminal by following command
npm install -g devtools-terminal
I get below error.
C:\Users\Anup\node_modules\devtools-terminal\node_modules\socket.io\node_modules
\socket.io-client\node_modules\ws>node "C:\nodejs\node_modules\npm\bin\node-gyp-
bin....\node_modules\node-gyp\bin\node-gyp.js" rebuild
npm ERR! not ok code 0
Thanks,
Anup
The text was updated successfully, but these errors were encountered: