-
Notifications
You must be signed in to change notification settings - Fork 0
Installation on windows failing #2
Comments
That's weird. What does running the following output for you? node -e "console.log(process.platform);" A value of Also, what terminal program are you using? Command Prompt, PowerShell, Cygwin, MinGW32, MSysGit, etc.? |
Oh, also: do you have |
Oh, I bet it also needs to run |
Do I need to do something else besides |
I believe the former combo should work until i get this patched. Does it not? :: From project dir
cd node_modules
git clone https://github.com/JamesMGreene/node-partty.git partty
cd partty
npm install Note that if you run a subsequent |
Can you try the new version |
(Hopefully fixed by 327a506) |
Unfortunately it didn't work:
|
Try deleting the whole "partty" directory and then do |
:(
|
Updated again. Could you try deleting the whole "partty" directory and then do |
Just tried this out on my own Windows box. For me, I saw the same installation errors for
|
Pulling out the actual failure to highlight it:
|
hmm, I end up with a MSBUILD error, even after installing .NET Framework 2.0 SDK:
|
Maybe you also need to add VCBuild parent directory to your |
BTW, here are the actual supposed build dependencies for the downstream winpty dependency (submodule): https://github.com/peters/winpty#prerequisites Pretty sure you should be able to build it without those, theoretically, though... but apparently it didn't work for me! 😖 |
I'm sorry for all the trouble I caused. It is getting far more complicated than I thought and with some changes not worth it for me anymore. I was hoping to see it being used within cloud commander as its current console implementation is super limited. |
Hey,
I tried to install it on a win 7 64bit machine but it always ends up with:
The text was updated successfully, but these errors were encountered: