Skip to content

Instantly share code, notes, and snippets.

@gravejester
Last active May 11, 2017 22:22
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save gravejester/817376ab62a0abd21f14f7a90a7e1081 to your computer and use it in GitHub Desktop.
Save gravejester/817376ab62a0abd21f14f7a90a7e1081 to your computer and use it in GitHub Desktop.
adm cmd:
install node for windows
- node v6.10.3
- npm 3.10.10
cd c:\..\..\EditorSyntax
npm init
npm install windows-build-tools --save
npm install vscode-textmate --save
C:\Users\ojk\Documents\GitHub\EditorSyntax>npm install vscode-textmate --save
> oniguruma@6.2.1 install C:\Users\ojk\Documents\GitHub\EditorSyntax\node_modules\oniguruma
> node-gyp rebuild
C:\Users\ojk\Documents\GitHub\EditorSyntax\node_modules\oniguruma>if not defined npm_config_node_gyp (node "C:\Program Files\nodejs\node_modules\npm\bin\node-gyp-bin\\..\..\node_modules\node-gyp\bin\node-gyp.js" rebuild ) else (node "" rebuild )
Building the projects in this solution one at a time. To enable parallel build, please add the "/m" switch.
TRACKER : error TRK0005: Failed to locate: "CL.exe". The system cannot find the file specified. [C:\Users\ojk\Documents
\GitHub\EditorSyntax\node_modules\oniguruma\build\oniguruma.vcxproj]
gyp ERR! build error
gyp ERR! stack Error: `C:\Program Files (x86)\MSBuild\14.0\bin\msbuild.exe` failed with exit code: 1
gyp ERR! stack at ChildProcess.onExit (C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\lib\build.js:276:23)
gyp ERR! stack at emitTwo (events.js:106:13)
gyp ERR! stack at ChildProcess.emit (events.js:191:7)
gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:215:12)
gyp ERR! System Windows_NT 10.0.16188
gyp ERR! command "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\node_modules\\node-gyp\\bin\\node-gyp.js" "rebuild"
gyp ERR! cwd C:\Users\ojk\Documents\GitHub\EditorSyntax\node_modules\oniguruma
gyp ERR! node -v v6.10.3
gyp ERR! node-gyp -v v3.4.0
gyp ERR! not ok
editorsyntax@1.0.0 C:\Users\ojk\Documents\GitHub\EditorSyntax
`-- fast-plist@0.1.2 extraneous
npm ERR! Windows_NT 10.0.16188
npm ERR! argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "install" "vscode-textmate" "--save"
npm ERR! node v6.10.3
npm ERR! npm v3.10.10
npm ERR! code ELIFECYCLE
npm ERR! oniguruma@6.2.1 install: `node-gyp rebuild`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the oniguruma@6.2.1 install script 'node-gyp rebuild'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the oniguruma package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node-gyp rebuild
npm ERR! You can get information on how to open an issue for this project with:
npm ERR! npm bugs oniguruma
npm ERR! Or if that isn't available, you can get their info via:
npm ERR! npm owner ls oniguruma
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR! C:\Users\ojk\Documents\GitHub\EditorSyntax\npm-debug.log
C:\>dir cl.exe /S /B
C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\VC\Tools\MSVC\14.10.25017\bin\HostX64\x64\cl.exe
C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\VC\Tools\MSVC\14.10.25017\bin\HostX64\x86\cl.exe
C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\VC\Tools\MSVC\14.10.25017\bin\HostX86\x64\cl.exe
C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\VC\Tools\MSVC\14.10.25017\bin\HostX86\x86\cl.exe
C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\Extensions\Microsoft\Microsoft Azure Data Lake Tools for Visual Studio 2015\2.1.0000.0\CppSDK\VC\bin\cl.exe
C:\>npm config get msvs_version
2015
npm install --global windows-build-tools
npm install vscode-textmate --save
[same errors]
Modify Visual Studio 2015 install:
- add visual c++
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment