github/atom
1
1
Fork 0
mirror of https://github.com/atom/atom.git synced 2026-01-23 05:48:10 -05:00
Code Issues Packages Projects Releases Wiki Activity

Update windows build instructions

Browse Source
This commit is contained in:
Corey Johnson
2014-05-14 15:34:19 -07:00
parent d015793851
commit 73f8c28add
1 changed files with 13 additions and 11 deletions
Download Patch File Download Diff File Expand all files Collapse all files

24
docs/build-instructions/windows.md
View File

@@ -20,21 +20,23 @@
## Why do I have to use GitHub for Windows? Can't I just use my existing Git?
You totally can! GitHub for Windows's Git Shell just takes less work to set up. You need to have Posix tools in your `%PATH%` (i.e. `grep`, `sed`, et al.), which isn't the default configuration when you install Git. To fix this, you probably need to fiddle with your system PATH.
You totally can! GitHub for Windows's Git Shell just takes less work to set up.
You need to have Posix tools in your `%PATH%` (i.e. `grep`, `sed`, et al.),
which isn't the default configuration when you install Git. To fix this, you
probably need to fiddle with your system PATH.
## Troubleshooting
Some of the most common errors include:
### Common Errors
* `node is not recognized`
gyp WARN install got an error, rolling back install
and
* If you just installed node you need to restart your computer before node is
available on your Path.
>> The system cannot find the path specified.
These two error messages can usually be ignored. The solution to these errors is to re-run `script\build`, possibly several times.
* `gyp WARN install got an error, rolling back install` or `The system cannot
find the path specified.`
If your Visual Studio is in a non-standard location, and you get the error `You must have Visual Studio 2010 or 2012 installed`, you need to modify `apm\node_modules\atom-package-manager\lib\config.js` around line 90 and replace the variable with your Visual Studio directory plus Common7/IDE.
Example:
vs2010Path = "H:/VS2010/Common7/IDE"
* These two error messages can usually be ignored. An admittedly hacky
solution to these errors is to re-run `script\build`, possibly several
times.