- Visual C++ 2010 Express
- Visual Studio 2010 Service Pack 1
- node.js v0.10.x
- For 64-bit builds of node and native modules you must have the Windows 7 64-bit SDK. You may also need the compiler update for the Windows SDK 7.1
- Python v2.7.
- The python.exe must be available at
%SystemDrive%\Python27\python.exe. If it is installed elsewhere, you can create a symbolic link to the directory containing the python.exe using:mklink /d %SystemDrive%\Python27 D:\elsewhere\Python27
- The python.exe must be available at
- GitHub for Windows
- Visual Studio Express 2013 for Windows Desktop
- node.js v0.10.x
- Python v2.7.x (required by node-gyp)
- GitHub for Windows
# Use the `Git Shell` app which was installed by GitHub for Windows. Also Make
# sure you have logged into the GitHub for Windows GUI App.
cd C:\
git clone https://github.com/atom/atom/
cd atom
script/build # Creates application in the `Program Files` directoryYou don't, You can use your existing Git! GitHub for Windows's Git Shell is just
easier 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.
-
node is not recognized- If you just installed node you need to restart your computer before node is available on your Path.
-
script/buildoutputs only the Node and Python versions before returning- Try moving the repository to
C:\atom. Most likely, the path is too long. See issue #2200.
- Try moving the repository to
-
error MSB4025: The project file could not be loaded. Invalid character in the given encoding.- These can occur because your home directory (
%USERPROFILE%) has non-ASCII characters in it. This is a bug in gyp which is used to build native node modules and there is no known workaround.
- These can occur because your home directory (
- Use this search to get a list of reports about build errors on Windows.