mirrors/electron
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

Add $ notation

Browse source
This commit is contained in:
Jessica Lord 2015-08-31 21:10:48 -07:00
parent 2c79e9fd41
commit 316210d6c4
1 changed files with 12 additions and 12 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

24
docs/development/build-instructions-windows.md
View file

@ -27,7 +27,7 @@ building with Visual Studio will come in the future.
## Getting the Code ## Getting the Code
```powershell ```powershell
git clone https://github.com/atom/electron.git $ git clone https://github.com/atom/electron.git
``` ```
## Bootstrapping ## Bootstrapping
@ -37,8 +37,8 @@ the build project files. Notice that we're using `ninja` to build Electron so
there is no Visual Studio project generated. there is no Visual Studio project generated.
```powershell ```powershell
cd electron $ cd electron
python script\bootstrap.py -v $ python script\bootstrap.py -v
``` ```
## Building ## Building
@ -46,13 +46,13 @@ python script\bootstrap.py -v
Build both Release and Debug targets: Build both Release and Debug targets:
```powershell ```powershell
python script\build.py $ python script\build.py
``` ```
You can also only build the Debug target: You can also only build the Debug target:
```powershell ```powershell
python script\build.py -c D $ python script\build.py -c D
``` ```
After building is done, you can find `electron.exe` under `out\D` (debug After building is done, you can find `electron.exe` under `out\D` (debug
@ -64,7 +64,7 @@ To build for the 64bit target, you need to pass `--target_arch=x64` when running
the bootstrap script: the bootstrap script:
```powershell ```powershell
python script\bootstrap.py -v --target_arch=x64 $ python script\bootstrap.py -v --target_arch=x64
``` ```
The other building steps are exactly the same. The other building steps are exactly the same.
@ -74,13 +74,13 @@ The other building steps are exactly the same.
Test your changes conform to the project coding style using: Test your changes conform to the project coding style using:
```powershell ```powershell
python script\cpplint.py $ python script\cpplint.py
``` ```
Test functionality using: Test functionality using:
```powershell ```powershell
python script\test.py $ python script\test.py
``` ```
Tests that include native modules (e.g. `runas`) can't be executed with the Tests that include native modules (e.g. `runas`) can't be executed with the
@ -90,7 +90,7 @@ details), but they will work with the release build.
To run the tests with the release build use: To run the tests with the release build use:
```powershell ```powershell
python script\test.py -R $ python script\test.py -R
``` ```
## Troubleshooting ## Troubleshooting
@ -128,8 +128,8 @@ This is caused by a bug when using Cygwin Python and Win32 Node together. The
solution is to use the Win32 Python to execute the bootstrap script (assuming solution is to use the Win32 Python to execute the bootstrap script (assuming
you have installed Python under `C:\Python27`): you have installed Python under `C:\Python27`):
```bash ```powershell
/cygdrive/c/Python27/python.exe script/bootstrap.py $ /cygdrive/c/Python27/python.exe script/bootstrap.py
``` ```
### LNK1181: cannot open input file 'kernel32.lib' ### LNK1181: cannot open input file 'kernel32.lib'
@ -141,7 +141,7 @@ Try reinstalling 32bit Node.js.
Simply making that directory [should fix the problem](http://stackoverflow.com/a/25095327/102704): Simply making that directory [should fix the problem](http://stackoverflow.com/a/25095327/102704):
```powershell ```powershell
mkdir ~\AppData\Roaming\npm $ mkdir ~\AppData\Roaming\npm
``` ```
### node-gyp is not recognized as an internal or external command ### node-gyp is not recognized as an internal or external command