In Visual C ++, there are two solutions to the error spawning cl.exe error.

Many people may have clicked "compile" or "build" after installing VC 6.0.
The error message "compiling..., error spawning cl.exe" is too depressing. Many people
Select to reinstall. In fact, this problem is often caused by path settings,
“Cl.exe "is the true compiler used by VC (compileProgramThe path is under "VC root directory \ vc98 \ bin,
You can find the application in the corresponding path.

Therefore, you can solve the problem as follows:

Method 1:

Open the VC interface and click VC "tools"-> "option )"
-> "Directories (directory)" to reset "excutable fils, include files,
Library files and source files. In many cases, a drive letter may be different.
(For example, if your VC is installed in C, but all these paths are in D), it will be OK.

If you install vc6.0 in the initial path, the path should be:
Executatble files:
C: \ Program Files \ Microsoft Visual Studio \ common \ msdev98 \ bin
C: \ Program Files \ Microsoft Visual Studio \ vc98 \ bin
C: \ Program Files \ Microsoft Visual Studio \ common \ tools
C: \ Program Files \ Microsoft Visual Studio \ common \ tools \ winnt

Include files:
C: \ Program Files \ Microsoft Visual Studio \ vc98 \ include
C: \ Program Files \ Microsoft Visual Studio \ vc98 \ MFC \ include
C: \ Program Files \ Microsoft Visual Studio \ vc98 \ ATL \ include

Library files:
C: \ Program Files \ Microsoft Visual Studio \ vc98 \ Lib
C: \ Program Files \ Microsoft Visual Studio \ vc98 \ MFC \ Lib

Source files:
C: \ Program Files \ Microsoft Visual Studio \ vc98 \ MFC \ SRC
C: \ Program Files \ Microsoft Visual Studio \ vc98 \ MFC \ include
C: \ Program Files \ Microsoft Visual Studio \ vc98 \ ATL \ include
C: \ Program Files \ Microsoft Visual Studio \ vc98 \ CRT \ SRC

If you install it on another disk, you just need to change it based on the path (I just installed it on disk D ).
The key is that Microsoft Visual Studio \ should follow the same things. Case sensitive.

Method 2: (this is relatively simple)

The easiest way: Do not use the GUI when starting the VC. Run msdev/useenv at the command prompt (note/there is a space in front ). it will force the system environment variable to be set to the correct value. in addition, you only need to run VC once, and then start it again by double-clicking the icon.

It seems that you still have to learn a lot!

 

This article is from the csdn blog,

Source:Http://blog.csdn.net/z2care/archive/2007/04/24/1576783.aspx