Mitch Gallant
2007-05-12 11:29:02 UTC
I have VS2005 installed and used it many times last year with no problems. I
just installed psdk WS2003 R2 (March 2006) and executed the "Visual Studio
Registration" shortcut to add the include, lib, bin etc paths for psdk to
Visual Studio.
I tried recompiling several C++ apps under VS2005 and can't compile any of
them now!
I get this compile error:
Project : error PRJ0003 : Error spawning 'cl.exe'.
This looks like a problem with the VC++ Directories location and so I looked
at:
Tool |Options
at the Projects and Solutions and VC++ Directories tree and there are only 2
entries in there now, related to the newly installed PSDK:
C:\Program Files\Microsoft Platform SDK for Windows Server 2003
R2\bin\winnt
C:\Program Files\Microsoft Platform SDK for Windows Server 2003 R2\bin
and there is no cl.exe compiler in those bin directories.
So is this the problem? Did the registration procedure above somehow nuke
the default entry for original bin directory where VS2005 looks for the
compiler (and linker) ??
What should be the setting for VS2005 for the Executable Binaries search
path? What other default directory search paths might have been effected?
Is there a way to restore the VS2005 bin (and other general search directory
settings)?
The specific added libs included in my projects are however still correct.
- Mitch Gallant
just installed psdk WS2003 R2 (March 2006) and executed the "Visual Studio
Registration" shortcut to add the include, lib, bin etc paths for psdk to
Visual Studio.
I tried recompiling several C++ apps under VS2005 and can't compile any of
them now!
I get this compile error:
Project : error PRJ0003 : Error spawning 'cl.exe'.
This looks like a problem with the VC++ Directories location and so I looked
at:
Tool |Options
at the Projects and Solutions and VC++ Directories tree and there are only 2
entries in there now, related to the newly installed PSDK:
C:\Program Files\Microsoft Platform SDK for Windows Server 2003
R2\bin\winnt
C:\Program Files\Microsoft Platform SDK for Windows Server 2003 R2\bin
and there is no cl.exe compiler in those bin directories.
So is this the problem? Did the registration procedure above somehow nuke
the default entry for original bin directory where VS2005 looks for the
compiler (and linker) ??
What should be the setting for VS2005 for the Executable Binaries search
path? What other default directory search paths might have been effected?
Is there a way to restore the VS2005 bin (and other general search directory
settings)?
The specific added libs included in my projects are however still correct.
- Mitch Gallant