Jump to content

  • Log In with Google      Sign In   
  • Create Account


What can cause visual studio to be unable to compile a Directx11 project?


Old topic!
Guest, the last post of this topic is over 60 days old and at this point you may not reply in this topic. If you wish to continue this conversation start a new topic.

  • You cannot reply to this topic
4 replies to this topic

#1 Veil   Members   -  Reputation: 143

Like
0Likes
Like

Posted 07 June 2012 - 01:15 AM

When I played around with sample Directx9 projects from tutorial sites,they would run with no problem,but whenever I try to compile a Directx11 project,I get

error MSB6006: "cmd.exe" exited with code 9009

Is there a way to fix this?Do I need some kind of patch for VS?
(I'm using Visual Studio 2010 on Windows 7 64 bit.)

Sponsor:

#2 mhagain   Crossbones+   -  Reputation: 7832

Like
0Likes
Like

Posted 07 June 2012 - 03:09 AM

Don't assume that VS is broken and needs patching - it's most likely your code and/or project settings. Why are you running it under a command shell? You'll need to post some code so that people can see what you're doing and comment further.

It appears that the gentleman thought C++ was extremely difficult and he was overjoyed that the machine was absorbing it; he understood that good C++ is difficult but the best C++ is well-nigh unintelligible.


#3 Veil   Members   -  Reputation: 143

Like
0Likes
Like

Posted 07 June 2012 - 08:13 AM

Don't assume that VS is broken and needs patching - it's most likely your code and/or project settings. Why are you running it under a command shell? You'll need to post some code so that people can see what you're doing and comment further.


I'm using Frank Luna's directx11 sample: http://www.d3dcoder.net/d3d11.html

Pretty much all of them give me this error,I'm trying to compile the GeometryShader example right now in Part1.

#4 amandip   Members   -  Reputation: 103

Like
0Likes
Like

Posted 07 June 2012 - 01:36 PM

This is most likely caused by missing executables under the build phase. Probably fxc.exe which is the DirectX effects compiler.

Do the following in VS2010:

Project -> Properties -> Configuration Properties -> VC++ Directories.

In "Executable Directories", add the path to the DirectX utilities bin folder, which is typically: "\Program Files (x86)\Microsoft DirectX SDK (June 2010)\Utilities\bin\x86". Be sure to check what it is exactly for your installation of DirectX. This folder contains fxc.exe and much more.
Apply changes and re-compile.

Other possible causes:
- Include directories
- Library directories
- Platform Toolset under Configuration Properties -> General, should be v100 or Windows7.1SDK.

All of the latter three possible causes have similar fixes to the first one described above, namely to specify the correct paths.

Edited by amandip, 07 June 2012 - 02:07 PM.


#5 DJTN   Members   -  Reputation: 207

Like
0Likes
Like

Posted 08 June 2012 - 09:54 AM

Frank precompiles the effects before use. Amandip's first suggestion should work.




Old topic!
Guest, the last post of this topic is over 60 days old and at this point you may not reply in this topic. If you wish to continue this conversation start a new topic.



PARTNERS