Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

cmd.exe exited with code 9009

I am trying to compile XNABasics project in visual studio from this repository https://code.google.com/p/kinect4bag/

But it gives me a error named:

Error 1 error MSB6006: "cmd.exe" exited with code 9009. C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\Microsoft.CppCommon.targets 151 6 CGePhysics

and when i double click it redirects me to the page given below, i have checked the project properties does not have anything in custom build step and custom build tool area.

enter image description here

like image 682
rajat Avatar asked Jul 06 '13 14:07

rajat


People also ask

How do I fix error code 9009?

How do I fix error code 9009? Download Outbyte PC Repair application See more information about Outbyte; uninstall instructions; EULA; Privacy Policy. Click the Scan Now button to detect issues and abnormalities. Click the Repair All button to fix the issues.

What is exit code 9009?

Error Code 9009 means error file not found. All the underlying reasons posted in the answers here are good inspiration to figure out why, but the error itself simply means a bad path.


2 Answers

When I had this problem it was due to missing Direct X executable paths in the property manager. As suggested at this Stack Overflow thread: MSB6006: “cmd.exe” exited with code 9009

Upon inspecting my build log I found that

'fxc' is not recognized as an internal or external command
which brought me to this solution: 'fxc.exe' is not recognized as an internal or external command

I went into my property manager to Microsoft.Cpp.Win32.user and added the proper DirectX SDK paths to Executables, Include, and Library (C:\Program Files\Microsoft DirectX SDK\Utilities\bin\x64, C:\Program Files\Microsoft DirectX SDK\Include, C:\Program Files\Microsoft DirectX SDK\Lib\x86 respectively)

like image 32
whotyjones Avatar answered Oct 10 '22 11:10

whotyjones


Just came across this thread now.

I had the exact same error. In my case, the swig.exe path that my project was looking for was wrong. My issue was fixed once i made sure the SWIG package was in the same path that my Project Properties' Macro was looking.

like image 116
Jag Avatar answered Oct 10 '22 11:10

Jag