Q: After I have installed BoundsChecker 5.0 I get the following message when I try to compile my project Deleting intermediate files and output files for project 'TestProg- Win32 Debug'. --------------------Configuration: TestProg - Win32 Debug-------------------- Compiling resources... Compiling... Error spawning cl.exe TestProg.exe - 1 error(s), 0 warning(s)
A: This occurs when you have DevStudio installed to the Program Files directory and there is a file called "Program" on the same drive and/or you also have BoundsChecker installed to a path containing a long filename. From our Readme.txt in the BoundsChecker directory: "Because of problems with Visual C++ and long file names, be sure to install BoundsChecker using short (8.3) names for install directories, if you plan on using the IDE integration or Smart Debugging. The BoundsChecker installation directory needs to be in your path if you plan to compile and link from the DOS command-line." Solution: search the drive where MSDEV/DevStudio is installed for everything named Program* (note the wildcard). Delete or rename the file(s) or directories; alternatively, reinstall MSDEV to a directory of its own (no Program Files). 看的明白吗？如果你没装boundchecker的话，就有可能是长文件名之类的，解决方法是不要把msstudio装到program开头的文件夹下
你的vc重装后，生殖系统出了问题，spawning.....(产卵)
：）帮你顶：）
--------------------Configuration: TestProg - Win32 Debug--------------------
Compiling resources...
Compiling...
Error spawning cl.exe TestProg.exe - 1 error(s), 0 warning(s)
A: This occurs when you have DevStudio installed to the Program Files directory and there is a file called "Program" on the same drive and/or you also have BoundsChecker installed to a path containing a long filename. From our Readme.txt in the BoundsChecker directory: "Because of problems with Visual C++ and long file names, be sure to install BoundsChecker using short (8.3) names for install directories, if you plan on using the IDE integration or Smart Debugging. The BoundsChecker installation directory needs to be in your path if you plan to compile and link from the DOS command-line." Solution: search the drive where MSDEV/DevStudio is installed for everything named Program* (note the wildcard). Delete or rename the file(s) or directories; alternatively, reinstall MSDEV to a directory of its own (no Program Files). 看的明白吗？如果你没装boundchecker的话，就有可能是长文件名之类的，解决方法是不要把msstudio装到program开头的文件夹下
http://www.sijiqing.com/vbgood/forum/forum_posts.asp?TID=644&PN=1