TRACKER : error TRK0005: Failed to locate: "CL.exe"

user_1647457 0
Viewed 12678

I feel like I've tried everything.

  • I have installed and uninstalled every single version of Visual studio (from 2010 - 2017)

  • I have attempted to install the build tools used for windows c++

  • I have uninstalled node.js and reinstalled.

BUT NO matter what I do I still get the error: 

TRACKER : error TRK0005: Failed to locate: "CL.exe".

I have attempted every "solution" i could find on google that discusses or descripe this issue.

When i run npm install

I get the following error: 

    TRACKER : error TRK0005: Failed to locate: "CL.exe". file not found


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.15063
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:\xampp\htdocs\myproject\src\node_modules\node-expat
gyp ERR! node -v v6.11.1
gyp ERR! node-gyp -v v3.4.0
gyp ERR! not ok
learningbank@1.0.0 C:\xampp\htdocs\myproject\src
`-- (empty)

Can anyone tell me how I can fix this issue?

My operation system is "Windows 10 pro".

node-gyp npm-install node.js c++
5 Answers

Today I had a comparable problem building a new 'Hello World' console application. I took a look in the property pages (View - Other Windows - Property Manager) at Microsoft.Cpp.Win32.user​. At Common Properties - VC++ Directories - Executable Directories it turned out that 'Inherit from parent or project defaults' was not checked. After checking that cl.exe was found.

user_107754540

I had the same problem. It was solved when I used visual studio 2015 instead of 2019 and also changed the windows SDK version from 10.0 to 8.1.

user_146269480
Related