在VC++6.0中,总是出现一个叫error spawning c1.exe的错误,怎么回事呢? vc6.0一直有error spawning c1.exe错...

\u4e3a\u4ec0\u4e48\u7f16\u8bd1\u548c\u8fd0\u884cvc++ \u65f6\u4f1a\u51fa\u73b0Error spawning c1.exe \u7684\u9519\u8bef

\u90a3\u4e2a\u4e0d\u53ebC1.exe,\u662fcl.exe\uff0c\u6587\u4ef6\u5728VC\u5b89\u88c5\u76ee\u5f55\u7684bin\u4e0b\u8fb9\uff0c\u8fd9\u79cd\u9519\u8bef\u4e00\u822c\u662f\u5728\u8fdb\u884c\u7f16\u8bd1\u65f6\u627e\u4e0d\u5230\u6587\u4ef6\u6240\u81f4\uff0c\u4e0d\u8fc7\u4e2a\u4eba\u8ba4\u4e3a\u5927\u591a\u6570\u662f\u7a0b\u5e8f\u4e2d\u4f7f\u7528\u4e86\u67d0\u4e00\u4e2a\u9759\u6001\u5e93\uff0c\u800c\u5728\u8fdb\u884c\u7f16\u8bd1\u7684\u65f6\u5019\u627e\u4e0d\u5230\u8be5\u9759\u6001\u5e93\u6240\u81f4\u3002
\u539f\u56e0\u662f\u8fd9\u4e9b\uff0c\u89e3\u51b3\u65b9\u6cd5\uff0c\u7f51\u4e0a\u8bf4\u7684\u57fa\u672c\u90fd\u6ca1\u9519\u3002Excutable file\u5c31\u662fVC\u5b89\u88c5\u76ee\u5f55\u4e0b\u7684bin\u76ee\u5f55\uff0cinclude Files\u662f\u5b89\u88c5\u76ee\u5f55\u4e0b\u7684include\u6587\u4ef6\u5939\uff0cLibrary Files\u662flib\u76ee\u5f55\uff0c Source Files\uff0c\u8bbe\u7f6e\u4e00\u4e0b\u81ea\u5df1\u5de5\u7a0b\u7684\u5f15\u7528\u76ee\u5f55\uff0c\u4e0d\u8fc7\u8fd9\u4e2a\u4e00\u822c\u5efa\u7acb\u5de5\u7a0b\uff0c\u8fdb\u884c\u6587\u4ef6\u52a0\u5165\uff0c\u5e76\u4e14insert into project\u7684\u8bdd\uff0c\u4e0d\u4f1a\u6709\u4ec0\u4e48\u95ee\u9898\u3002
\u6700\u540e\u5efa\u8bae\uff0c\u91cd\u65b0\u5b89\u88c5VC\uff0c\u8fd9\u662f\u6700\u597d\u7684\u65b9\u5f0f\u3002\u5982\u679c\u8fd8\u6709\u95ee\u9898\uff0c\u5e94\u8be5\u5c31\u662f\u7a0b\u5e8f\u7684\u95ee\u9898\u4e86\u3002

\u51fa\u73b0\u8fd9\u79cd\u95ee\u9898\u7684vc6\u4e00\u822c\u662f\u6240\u8c13\u7684\u7eff\u8272\u7248\u7cbe\u7b80\u7248\uff08\u5176\u5b9e\u73b0\u5728\u7684\u7eff\u8272\u7248\u5f88\u591a\u4e5f\u8981\u5199\u6ce8\u518c\u8868\u548c\u8bbe\u7f6e\u4e00\u4e9b\u7cfb\u7edf\u914d\u7f6e\uff09\uff0c\u51fa\u73b0\u7f16\u8bd1\u4e0d\u901a\u8fc7\u7684\u539f\u56e0\u4e3b\u8981\u662fvc6\u7684\u914d\u7f6e\u6587\u4ef6\u6ca1\u6709\u8bbe\u7f6e\u597d\uff0c\u4e00\u4e9b\u5efa\u8bae\u91cd\u88c5\u4e4b\u7c7b\u7684\u65b9\u6cd5\u6709\u70b9\u8bef\u4eba\u5b50\u5f1f\u3002
\u6253\u5f00vc\u754c\u9762 \u70b9\u51fbVC\u201cTOOLS\uff08\u5de5\u5177\uff09\u201d\u2014>\u201cOption\uff08\u9009\u9879\uff09\u201d \u2014>\u201cDirectories\uff08\u76ee\u5f55\uff09\u201d\u91cd\u65b0\u8bbe\u7f6e\u201cExcutable Fils(\u53ef\u6267\u884c\u6587\u4ef6)\u3001Include Files\u3001
Library Files\u3001Source Files\u201d\u7684\u8def\u5f84(\u6ce8\u610f\u8fd9\u4e9b\u662f\u4e0b\u62c9\u6846\u6846\u91cc\u53ef\u4ee5\u9009\u7684\u54e6)\u3002\u5f88\u591a\u60c5\u51b5\u53ef\u80fd\u5c31\u4e00\u4e2a\u76d8\u7b26\u7684\u4e0d\u540c
\uff08\u4f8b\u5982\u4f60\u7684VC\u88c5\u5728C\uff0c\u4f46\u662f\u8fd9\u4e9b\u8def\u5f84\u5168\u90e8\u5728D\uff09\uff0c\u6539\u8fc7\u6765\u5c31OK\u4e86\u3002
\u5982\u679c\u4f60\u662f\u6309\u7167\u521d\u59cb\u8def\u5f84\u5b89\u88c5vc6.0\u7684\uff0c\u8def\u5f84\u5e94\u4e3a\uff1a (\u6709\u4e0b\u753b\u7ebf\u7684\u81ea\u5df1\u53bb\u627e\u4f60\u7684\u76f8\u5e94\u7684\u76ee\u5f55)
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

\u5982\u679c\u4f60\u88c5\u5728\u5176\u4ed6\u76d8\u91cc\uff0c\u5219\u4eff\u7167\u5176\u8def\u5f84\u53d8\u901a\u5c31\u884c(\u6211\u5c31\u662f\u88c5\u5728D\u76d8)\u3002
\u5173\u952e\u662fmicrosoft visual studio\ \u540e\u9762\u7684\u4e1c\u897f\u8981\u76f8\u540c\uff0c\u4f8b\u5982\u4f60\u7684\u76ee\u5f55\u662fE:\vc6,\u5c31\u628a\u4e0b\u5212\u7ebf\u7684\u90e8\u5206\u6362\u6210E:\vc6\u3002

楼上正解
我这里有基本错误的解决办法
以后一定会用到:

在创建项目时, 不使用MFC AppWizard向导, 如果没有设置好项目参数, 就会在编译时产生很多连接错误, 如error LNK2001错误, 典型的错误提示有:
libcmtd.lib(crt0.obj) : error LNK2001: unresolved external symbol _main
LIBCD.lib(wincrt0.obj) : error LNK2001: unresolved external symbol _WinMain@16
msvcrtd.lib(crtexew.obj) : error LNK2001: unresolved external symbol _WinMain@16
nafxcwd.lib(thrdcore.obj) : error LNK2001: unresolved external symbol __beginthreadex
nafxcwd.lib(thrdcore.obj) : error LNK2001: unresolved external symbol __endthreadex

下面介绍解决的方法:
1. Windows子系统设置错误, 提示:
libcmtd.lib(crt0.obj) : error LNK2001: unresolved external symbol _main
Windows项目要使用Windows子系统, 而不是Console, 可以这样设置:
[Project] --> [Settings] --> 选择"Link"属性页,
在Project Options中将/subsystem:console改成/subsystem:windows

2. Console子系统设置错误, 提示:
LIBCD.lib(wincrt0.obj) : error LNK2001: unresolved external symbol _WinMain@16
控制台项目要使用Console子系统, 而不是Windows, 设置:
[Project] --> [Settings] --> 选择"Link"属性页,
在Project Options中将/subsystem:windows改成/subsystem:console

3. 程序入口设置错误, 提示:
msvcrtd.lib(crtexew.obj) : error LNK2001: unresolved external symbol _WinMain@16
通常, MFC项目的程序入口函数是WinMain, 如果编译项目的Unicode版本, 程序入口必须改为wWinMainCRTStartup, 所以需要重新设置程序入口:
[Project] --> [Settings] --> 选择"C/C++"属性页,
在Category中选择Output,
再在Entry-point symbol中填入wWinMainCRTStartup, 即可

4. 线程运行时库设置错误, 提示:
nafxcwd.lib(thrdcore.obj) : error LNK2001: unresolved external symbol __beginthreadex
nafxcwd.lib(thrdcore.obj) : error LNK2001: unresolved external symbol __endthreadex
这是因为MFC要使用多线程时库, 需要更改设置:
[Project] --> [Settings] --> 选择"C/C++"属性页,
在Category中选择Code Generation,
再在Use run-time library中选择Debug Multithreaded或者multithreaded
其中,
Single-Threaded 单线程静态链接库(release版本)
Multithreaded 多线程静态链接库(release版本)
multithreaded DLL 多线程动态链接库(release版本)
Debug Single-Threaded 单线程静态链接库(debug版本)
Debug Multithreaded 多线程静态链接库(debug版本)
Debug Multithreaded DLL 多线程动态链接库(debug版本)
单线程: 不需要多线程调用时, 多用在DOS环境下
多线程: 可以并发运行
静态库: 直接将库与程序Link, 可以脱离MFC库运行
动态库: 需要相应的DLL动态库, 程序才能运行
release版本: 正式发布时使用
debug版本: 调试阶段使用

VC 6.0“Compiling... ,Error spawning cl.exe”错误解决
Posted on 2005-06-03 19:55 k_eckel 阅读(8862) 评论(100) 编辑 收藏
可能很多人在安装VC 6.0后有过点击“Compile”或者“Build”后被出现的“Compiling... ,Error spawning cl.exe”错误提示给郁闷过。很多人的选择是重装,实际上这个问题很多情况下是由于路径设置的问题引起的,“CL.exe”是VC使用真正的编译器(编译程序),其路径在“VC根目录\VC98\Bin”下面,你可以到相应的路径下找到这个应用程序。
因此问题可以按照以下方法解决:点击VC“TOOLS(工具)”—>“Option(选择)”—>“Directories(目录)”重新设置“Excutable Fils、Include Files、Library Files、Source Files”的路径。很多情况可能就一个盘符的不同(例如你的VC装在C,但是这些路径全部在D),改过来就OK了。

nafxcw.lib(appcore.obj) : error LNK2001: unresolved external symbol ___argv
解决方法:

在Preprocessor中定义_AFXDLL

如果它提示:
fatal error C1189: #error : Please use the /MD switch for _AFXDLL builds

就这样改:

C/C++->Code Generation->Multithread DLL (即实现/MD选项)

Visual C++ Error MessagesThis page contains a listing of "difficult to diagnose" error messages and possible fixes. I haven't taught a programming class that uses Visual C++ in several years so this list is probably out of date by now. It was valid for Microsoft Visual C++ version 6.0 service pack 3.

--------------------------------------------------------------------------------

C1001: INTERNAL COMPILER ERROR (compiler file 'msc1.cpp', line 1786) Please choose the Technical Support command on the Visual C++ Help menu, or open the Technical Support help file for more information

This error results from leaving off the parentheses immediately following the function name in a function header. To correct the error simply add () to the end of the function name.

--------------------------------------------------------------------------------

C1010: unexpected end of file while looking for precompiled header directive

If your project is an MFC AppWizard created project then this error results from not #including StdAfx.h as the first #i nclude statement (before any other #i ncludes, data declarations, or executable program code).

--------------------------------------------------------------------------------

C1083: Cannot open precompiled header file: 'Debug/<Project-Name>.pch': No such file or directory

This error results from a missing file - the compiled version of StdAfx.cpp. Visual C++ does a poor job of keeping track of this file and frequently "forgets" how to build it. This problem often occurs after restoring a saved workspace from diskette without the Debug directory. To fix the error select StdAfx.cpp from the workspace file list them choose Compile from the Build menu. If that doesn't work the go to Project -> Settings, select the C/C++ tab, and click the radio button labeled Create Precompiled Headers.

--------------------------------------------------------------------------------

C2001: newline in constant

This error is usually caused by a string or character constant that is missing its closing ' or " symbol.

--------------------------------------------------------------------------------

C2065: '<data-member name>' : undeclared identifier

If this error occurs in one of your member functions then it is generally the result of forgetting the class scope operator in front of the function name in your .cpp file.

--------------------------------------------------------------------------------

C2143: syntax error : missing ';' before 'PCH creation point'

Check each of the #i nclude files to ensure that the closing brace of each class declaration is followed by a semicolon.

--------------------------------------------------------------------------------

C2143: syntax error : missing ';' before '*'

If this error is followed by two C2501 errors then the problem is an undeclared class name within a pointer declaration.

For example, the declaration:

CClass *pObject;

will generate the above error message followed by a C2501 error message for 'CClass' and another C2501 message for 'pObject'. The problem is that the compiler isn't recognizing CClass as a valid class/type name. To correct the problem add a #i nclude of the file containing the declaration of CClass (e.g., #i nclude CClass.h)

--------------------------------------------------------------------------------

C2447: missing function header (old-style formal list?)

This error usually results from a missing { or use of a ; instead of a { following the parameter list of a function header.

--------------------------------------------------------------------------------

C2511: '<function-name>' : overloaded member function not found in '<class-name>'

This error results from a mismatch in the parameter list of a member function declaration (.h file) and definition (.ccp file). Check the forward declaration of the function in the .h file and its definition in the .cpp file and ensure that the number of parameters and the type of each parameter match exactly.

--------------------------------------------------------------------------------

C2512: '<constructor-function-name>' : no appropriate default constructor available

This error usually occurs when you implement the constructor function of a derived class and forget to include parameter passing to the base class constructor function. For example assume that CDerived is derived from CBase and that the CBase constructor function requires one parameter (e.g., int A). If you define the CDerived constructor function as:

CDerived::CDerived(int A, int B) { ... }

the compiler will issue the above error message on the line containing the function header of CDerived::CDerived() because you haven't provided instructions for routing the parameter A to CBase::CBase(). Because you didn't provide instructions the compiler assumes that CBase::CBase() requires no arguments and it complains because no version of CBase::CBase() has been defined that accepts zero arguments.

If you intended to provide a version of CBase::CBase() that requires no arguments then the error message indicates that you forgot to declare that function in your base class declaration (e.g., in CBase.h).

If CBase::CBase() does require one or more arguments then you must correct the problem by including explicit instructions for passing parameters from the derived class constructor function to the base class constructor function. The correction for the example above is:

CDerived::CDerived(int A, int B) : CBase(A) { ... }

--------------------------------------------------------------------------------

C2556: '<function-name>' : overloaded functions only differ by return type
C2371: '<function-name>' : redefinition; different basic types

These errors usually result from a mismatch of function type between a .h and .cpp file. Check the forward declaration of the function in the .h file and its definition in the .cpp file and make the function return type identical in both files.

--------------------------------------------------------------------------------

C2601: '<function-name>' : local function definitions are illegal

This error results from defining one function inside the body of another function. It usually means that you omitted one or more } symbols in the function just before the function named in the error message.

--------------------------------------------------------------------------------

C2653: '<Class-Name>' : is not a class or namespace name

This error usually results from not having #i nclude "StdAfx.h" as the first #i nclude statement in your class.cpp file. It can also occur if your class definition is in a .h file and you forget to #i nclude that .h file in another file that refers to the class name.

--------------------------------------------------------------------------------

C2661: '<Class-Name>::<Function-Name>' : no overloaded function takes n parameters

This error indicates a mismatch between the parameters used in a function call (e.g., from main.cpp) and the declaration of the function. The function call is passing n parameters and there is no function declaration that uses that number of parameters.

--------------------------------------------------------------------------------

LNK1104: Cannot open file nafxcwd.lib

This error sometimes occurs when a project uses a class from the MFC but the project settings don't explicitly tell the link editor to look in the MFC libraries.

Go to Project --> Settings (Build --> Settings in Visual C++ 4.0). On the General tab check the box that says "Use MFC in a Shared DLL".

--------------------------------------------------------------------------------

LNK1168: cannot open Debug\<Project-Name>.exe for writing

This error occurs when the link editor attempts to write to a .exe file that is currently in use. The .exe file of an executing program is write protected until the program is terminated. Look at the status bar at the bottom of your screen and find the icon representing your executable application. Open the application and exit from it. Then select Build.

--------------------------------------------------------------------------------

LNK2001: unresolved external symbol __endthreadex
LNK2001: unresolved external symbol __beginthreadex

These errors result from using an MFC object or function without telling the link editor to search the MFC libraries.

Go to Project --> Settings (Build --> Settings in Visual C++ 4.0). On the General tab check the box that says "Use MFC in a Shared DLL".

--------------------------------------------------------------------------------

LNK2001: unresolved external symbol _main

Your project doesn't contain a function called main(). The error usually results from forgeting to add main.cpp to the project workspace.

--------------------------------------------------------------------------------

<File>.obj : error LNK2001: unresolved external symbol "public: void __thiscall <Class1>::<Function1>(<Type>)"

This a generic form of a LNK2001 error where <File>.obj can be any object file in your project and <Class1>::<Function1>(<Type>) can be any function in any class. Substitute the specific <File>, <Class>, <Function>, and <Type> in your message into the instructions below to diagnose and correct the problem.

An LNK2001 error means that the link editor is looking for a compiled function and can't find it. The call to the "missing function" is somewhere in <File>.cpp. Unfortunately, double-clicking on the error message won't take you to the point in <File.cpp> where the function is called but you can search for it with Find or Find In Files. The function the link editor can't find is a member of <Class>, its name is <Function1>, and its return type is <Type>.

There are two common reasons for a LNK2001 error:

The call in <File>.cpp doesn't match the function prototype in <Class>.h and/or the implementation in <Class>.cpp. The mismatch may be in the function name, return type, or number and/or type of parameters. Correction strategies include:
Check that the function name is spelled the same (case sensitive) in all three files (File.cpp, Class.h, and Class.cpp).
Check that the function is actually declared and defined within <Class> - perhaps you defined it as a member of a different class or perhaps you tried to call the function (in <File>.cpp) using an object or object pointer of a different class.
Check that the number and type of parameters in the function implementation (in <Class>.cpp) matches the number and type of parameters declared in the function declaration in <Class>.h.
Check that the number and type of parameters in the function call (in <File>.cpp) matches the number and type of parameters declared in the function header in <Class>.cpp.
The function was never declared or was declared but never defined. To see if either is the case go to the ClassView window of the Workspace view. Click the + next to <Class> and find <Function> in the list of member functions.
If <Function> is NOT in the list then it was never declared or defined - add a declaration to the class declaraion in <Class>.h and implement the function in <Class>.cpp.
If <Function> is in the list then right click on it and select Go To Definition from the pop-up menu. If you get the error message Cannot find definition (implementation) of this function then the function was declared but never defined (implemented). Implement the function to <Class>.cpp.

--------------------------------------------------------------------------------

LNK2005: <some-long-string-of-mostly-garbage> already defined in <name>.lib(<name>.obj)

This error usually results from including a source code file multiple times. If you recognize any of the names in the message then it probably results from multiple inclusion of one of your own header files. Check to be sure that you've used #ifndef/#define/#endif properly your header files. If you don't recognize the name then it's probably multiple inclusion of a system file (e.g., afxwin.h). Make sure that you haven't explicitly included something in main.cpp that is already included in one of your own header files. Also check that you haven't #i ncluded a .cpp file where you should have #i ncluded a .h file.

可能很多人在安装VC 6.0后有过点击“Compile”或者“Build”后被出现的“Compiling... ,Error spawning cl.exe”错误提示给郁闷过。很多人的选择是重装,实际上这个问题很多情况下是由于路径设置的问题引起的,“CL.exe”是VC使用真正的编译器(编译程序),其路径在“VC根目录\VC98\Bin”下面,你可以到相应的路径下找到这个应用程序。
因此问题可以按照以下方法解决:点击VC“TOOLS(工具)”—>“Option(选择)”—>“Directories(目录)”重新设置“Excutable Fils、Include Files、Library Files、Source Files”的路径。很多情况可能就一个盘符的不同(例如你的VC装在C,但是这些路径全部在D),改过来就OK了。
参考资料:http://www.mscenter.edu.cn/blog/k_eckel/articles/3016.html

  • 鍦╒C++6.0涓,鎬绘槸鍑虹幇涓涓彨error spawning c1.exe鐨勯敊璇,鎬庝箞鍥炰簨鍛...
    绛旓細瀹為檯涓婅繖涓棶棰樺緢澶氭儏鍐典笅鏄敱浜庤矾寰勮缃殑闂寮曡捣鐨锛屸淐L.exe鈥濇槸VC浣跨敤鐪熸鐨勭紪璇戝櫒锛堢紪璇戠▼搴忥級锛屽叾璺緞鍦ㄢ淰C鏍圭洰褰昞VC98\Bin鈥濅笅闈紝浣犲彲浠ュ埌鐩稿簲鐨勮矾寰勪笅鎵惧埌杩欎釜搴旂敤绋嬪簭銆傚洜姝ら棶棰樺彲浠ユ寜鐓т互涓嬫柟娉曡В鍐筹細鐐瑰嚮VC鈥淭OOLS锛堝伐鍏凤級鈥濃>鈥淥ption锛堥夋嫨锛夆濃>鈥淒irectories锛堢洰褰曪級鈥濋噸鏂拌缃淓xcuta...
  • 鍦╒C++6.0涓,鎬绘槸鍑虹幇涓涓彨error spawning c1.exe鐨勯敊璇,鎬庝箞鍥炰簨鍛...
    绛旓細鍙兘寰堝浜哄湪瀹夎VC 6.0鍚鏈杩囩偣鍑烩淐ompile鈥濇垨鑰呪淏uild鈥濆悗琚鍑虹幇鐨勨淐ompiling... ,Error spawning cl.exe鈥濋敊璇彁绀虹粰閮侀椃杩囥傚緢澶氫汉鐨勯夋嫨鏄噸瑁,瀹為檯涓婅繖涓棶棰樺緢澶氭儏鍐典笅鏄敱浜庤矾寰勮缃殑闂寮曡捣鐨,鈥淐L.exe鈥濇槸VC浣跨敤鐪熸鐨勭紪璇戝櫒(缂栬瘧绋嬪簭),鍏惰矾寰勫湪鈥淰C鏍圭洰褰昞VC98\Bin鈥濅笅闈,浣犲彲浠ュ埌鐩稿簲鐨勮矾寰勪笅...
  • 鎮祻100鍒,杩愯VC6.0鏃鎬绘湁涓涓敊璇︹﹂珮鎵嬭鍥炵瓟
    绛旓細Library Files銆丼ource Files鈥濈殑璺緞銆傚緢澶氭儏鍐靛彲鑳藉氨涓涓洏绗︾殑涓嶅悓 锛堜緥濡備綘鐨VC瑁呭湪C锛屼絾鏄繖浜涜矾寰勫叏閮ㄥ湪D锛夛紝鏀硅繃鏉ュ氨OK浜嗐傚鏋滀綘鏄寜鐓у垵濮嬭矾寰勫畨瑁vc6.0鐨勶紝璺緞搴斾负锛歟xecutatble files:C:\Program Files\Microsoft Visual Studio\Common\MSDev98\Bin C:\Program Files\Microsoft Visual Stud...
  • VC++6.0涓鍐欏叆绋嬪簭,缂栬瘧鍚庢彁绀鏈変竴閿欒,1 error(s)鎬庝箞绠鍗曠殑鎸囧嚭閿欒...
    绛旓細缂栬瘧鍑虹幇閿欒,鐩存帴鎸塅4,鍗冲彲瀹氫綅鍚勯敊璇銆1銆侀鍏堬紝杩涜鎵撳紑涓涓渶瑕佽繘琛岃皟璇曠殑浠g爜锛岃繘琛屽啀褰撳墠鏉ヨ繘琛岀紪杈戙2銆佸湪褰撳墠鐨勪唬鐮佽繘琛岀紪杈戠殑瀹屾垚锛岃繘琛岀偣鍑 run 鑿滃崟銆3銆佽繘琛岀偣鍑讳簡run涔嬪悗锛寮瑰嚭浜嗕笅鎷夎彍鍗曢変腑涓 debug 鐨勯夐」銆4銆佽繖鏍峰氨浼氬脊鍑轰簡涓涓渶瑕佺殑杩愯鐨勬枃浠跺悕绉颁腑锛岃繘琛岄変腑涓涓綋鍓嶇殑杩愯鍚嶇О銆
  • VC++6.0涓,鎬绘槸鍑虹幇涓涓彨error spawning c1.exe鐨勯敊璇,鑰屼笖鎴戠湅璺緞...
    绛旓細浣犺繖涓槸缁胯壊鐗堢殑VC锛鏄厤缃笉瀵圭殑闂锛屾渶绠鍗曠殑瑙e喅鍔炴硶鐢ㄥ師鐗堢殑VC6.0瀹夎锛屽氨涓嶄細鍑虹幇杩欎釜闂銆傛垜缁欎綘涓涓櫨搴︿簯瀹樻柟鍘熺増鐨刅C6.0銆
  • 鐢╲isual c++6.0缂栫▼搴鎬绘槸鏄剧ず1error(s),鍙槸鎴戝拰涔︿笂瀵逛簡鏄竴鏍风殑鍛...
    绛旓細include<iostream> 鐒跺悗杩樻湁涓棶棰鍑虹幇鍦ㄦ渶鍚庝竴琛岋紝杩欎釜閿欒鏈鐐逛綆绾у晩锛屽懙鍛靛懙銆傘傘傛墦瀛楅敊璇俽eturn 0;涓嬮潰鏄垜淇敼鍚庤繍琛屾垚鍔熺殑浠g爜锛歩nclude<iostream> using namespace std;int main(){ int num,count1=0,count2=0;double sum=0.0,ave=0.0;cout<<"璇疯緭鍏ヨ嫢骞叉暣鏁帮紝浠0缁撴潫:\n";cin >>...
  • 鍦╒C++6.0涓嬭繍琛岃繖娈电▼搴鎬绘槸鍑虹幇涓涓璇濇,璇碭X.exe宸插仠姝㈠伐浣,浣...
    绛旓細printf("杈撳叆涓涓鎻掑叆鐨勬暟锛");scanf("%d",&x);printf("\n");for (i=0;i<10;i++){ if (x<=a[i])//鍥犱负鍘熸潵鏁扮粍宸茬粡鏈搴,鏁呭彧闇浠庡乏閬撳彸閬嶅巻涓娆″嵆鍙紒{ for (j=9;j>=i;j--)//鎵惧埌浣嶇疆锛屽悗绉诲厓绱(娉ㄦ剰a[10]鏄负0)a[j+1]=a[j];break;} } a[i]=x;//鍦╥浣嶇疆...
  • c++鍦╒C6.0涓嚭鐜鏃犳硶鎵ц绋嬪簭
    绛旓細c++鍦╒C6.0涓嚭鐜鏃犳硶鎵ц绋嬪簭鏄缃敊璇犳垚鐨勶紝瑙e喅鏂规硶涓;1銆VC++6.0涓婂嚭鐜版彁绀衡滄棤娉曟墽琛岀▼搴忊濓紝寰堝彲鑳芥槸鍒涘缓宸ョ▼鍜屾枃浠剁殑鏃跺欓夋嫨閿欎簡锛屾敞鎰忚繍琛孋鍜孋++鐨勬槸.cpp鏂囦欢锛屼笉鏄.h銆2銆佸湪鍒涘缓宸ョ▼鐨勬椂鍊欐牴鎹渶瑕侀夋嫨Win32 Console Application銆3銆佸彧鏄竴浜涚畝鍗曠殑灏忕▼搴忕殑璇濓紝閫夋嫨C++Source File鍒涘缓婧...
  • 涓轰粈涔堟垜鐨vc++6.0鎬绘槸鏄剧ず鏈変竴涓敊璇,缂栬瘧涓嶄簡?
    绛旓細涓嶈繃澶存枃浠舵瘡涓汉閮戒笉涓鏍凤紝鍍忎箣鍓嶆垜鍒氫拱鐢佃剳锛屾垜鍚屽鐩存帴鏀惧湪妗岄潰锛岀紪璇戠幆澧冨氨鐩存帴鎸囧悜妗岄潰锛屼笉绠℃垜鏄噸瑁呰繕鏄粈涔堬紝閮芥槸鎸囧悜妗岄潰锛岄渶瑕佽嚜宸辨墜鍔ㄦ敼鍥炴潵锛屼笉杩囨湁浜涗笢瑗挎槸涓嶇敤鍙橈紝涓句緥E:\Microsoft Visual Studio\VC98\INCLUDE锛岃屾垜鐨勬槸D:\vc\VC98\Include銆傚儚鎴戠洿鎺ュ湪D鐩樻悶涓獀c鏂囦欢澶癸紝鍏朵粬涓嶇敤鏀癸紝...
  • 涓轰粈涔鍦╒C++6.0涓嬬紪璇戠▼搴忎細鍑虹幇杩欎釜闂
    绛旓細鍑虹幇杩欎釜闂搴旇鏄洜涓鸿妯″潡娌℃湁鍖呮嫭棰勭紪璇戝ご鏂囦欢鈥渟tdafx.h鈥濈殑缂樻晠锛屽湪VC涓槸鐢ㄤ竴涓猻tdafx.cpp鍖呭惈澶存枃浠秙tdafx.h锛岀劧鍚庡湪stdafx.h閲屽寘鍚ぇ閮ㄥ垎绯荤粺澶存枃浠讹紝杩欐牱缂栬瘧鏃禫C灏遍氳繃缂栬瘧stdafx.cpp鎶婂ぇ閮ㄥ垎绯荤粺澶存枃浠堕缂栬瘧杩涙潵浜嗭紝鍦―ebug鐩綍涓鏈 涓涓緢澶х殑鏂囦欢*.pch锛岃繖閲屽氨瀛樺偍浜嗛缂栬瘧淇℃伅锛屽鏋淧CH...
  • 扩展阅读:visualc++6.0官方下载 ... c++编程器手机版下载 ... vc++6.0安装教程 ... vc++6.0怎么安装 ... 电脑缺少vc++运行库怎么办 ... vc++6.0不兼容怎么办 ... 为什么visual c6.0打不开 ... microsoft visual c是什么 ... 微软visual c++运行错误 ...

    本站交流只代表网友个人观点,与本站立场无关
    欢迎反馈与建议,请联系电邮
    2024© 车视网