-
Notifications
You must be signed in to change notification settings - Fork 682
Cannot install on Windows #56
Comments
I believe 5903a22 should fix things for you. My test environment was:
The root
In particular, you should not have to run it as an administrator! In particular, I suspect it might cause other problems down the road if you do. |
Updated master to the latest, still not working.
|
@milesj What happens when you run the failed I identified some common problems people were having at #23 (comment). |
I use NPM/Node constantly, even before attempting to install this. I could try uninstalling and reinstalling to see if it makes a difference. |
For good measure, could you run |
I'll reopen. |
Still getting the same error. I have a pretty unusual setup, so I'm wondering if that's the issue. All of my programs are installed to E: instead of C:, so maybe it's a cross drive permissions issue? Are there any logs being written that I can dig into? Also running
|
Late today I updated the scripts to provide a little more info on failure. On Friday, June 12, 2015, Miles Johnson notifications@github.com wrote:
|
Also, are there any spaces in your paths??? On Friday, June 12, 2015, Michael Bolin bolinfest@gmail.com wrote:
|
There are some spaces in my paths but none of which related to these tools. Here's both my user and system paths.
|
I believe I found the issue. Gimme a few minutes. |
Yeah, turned out that git wasn't in my path. That error wasn't apparent till I tried running Sorry about that. Perhaps if there's a way to grab the error message from |
Ah ha, thanks! I believe there is one transitive Node dependency that is Out of curiosity, how did you choose to clone the Nuclide repo if Git isn't On Friday, June 12, 2015, Miles Johnson notifications@github.com wrote:
|
I just re-read your post. I guess SourceTree caused the problem? On Friday, June 12, 2015, Michael Bolin bolinfest@gmail.com wrote:
|
SourceTree uses its own Git, so cloning that is no issue. Once I started using the command line outside of SourceTree (Windows cmd prompt), Git was no longer available. |
FYI, it is this transitive dependency in a
So I'm updating the System Requirements to reflect this. |
Nice find. Is there a way for Nuclide to include that dependency manually and avoid Git while having the package that requires it use the local one? Not sure how much customization NPM allows unlike Composer. |
@milesj Yes! I moved our test runner (that depends on If you use So I'm not sure if this fixes things for you in the developer case, but it will fix things for users who install the prebuilt packages via Atom and do not have Git on their |
This is my setup:
Windows 7
Python 2.7.2 installed to C:\Python27
Node.js 0.12.4 and NPM 2.10.1 installed via the Windows installer
Atom 0.208.0 and APM 0.171.0 installed via the Windows installer
I keep receiving the following errors when executing the
scripts\dev\setup
file. I'm also running this as an administration through the command prompt.My projects are installed to a separate drive, the E: drive, so I'm curious if that's an issue in itself.
I've also tried this patch found in another issue, no go. https://github.com/apuckey/nuclide/commit/f33bdcef41125de52724e36a224f0f2688d03124
Any help would be appreciated.
The text was updated successfully, but these errors were encountered: