Kommentare zu: Windows SDK 7 messed up

Von: Neil

Neil — Sat, 22 Jan 2011 09:54:01 +0000

the script has some errors, so

SET “VCTools=%VCRoot%Bin”

should be

SET “VCTools=%VCRoot%\Bin”

This means that bin is not found and hence the “compilers are not [seemingly] installed”. There are other problems in the script (look for ‘!’ where you would expect ‘%’) which come up later on.

HTH.

Von: Marsh Ray

Marsh Ray — Tue, 23 Mar 2010 14:05:48 +0000

Notice that the installed “CMD Shell” shortcut isn’t to a .cmd file, but is instead to
cmd.exe /E:ON /V:ON /T:0E /K setenv.cmd

Setenv.cmd must be run from a command prompt interpreter which has delayed expansion enabled. It doesn’t check for this error condition though, it just fails silently.

Von: Martin

Martin — Tue, 23 Feb 2010 12:20:33 +0000

I recently had the same problem when I tryed to compile custom c-code based functions for the simulation software FLUENT. From what I gathered on the web, only a full SDK install provides you with all files.
I guess I did the same as you and selected only the files which I thought would be necessary. “Da haben wir wohl mal wieder die Rechnung ohne den Wirt gemacht” is all I can say .
Compiling plain C code however, did not affect my path variables…