.plg 是编译信息文件,编译时的error和warning信息文件(实际上是一个html文件),一般用处不大.
在Tools-＞Options里面有个选项可以控制这个文件的生成；
|
vc++ compile log
question 1: When I compile my C program with without MFC support. In the build question 2: When I compile with MFC support. In the build log file ( test.plg). "D:\vc\test\unchain.cpp" thanks . |
|
| Sat, 21 Feb 2004 04:54:06 GMT | |
 |
|
 vc++ compile logI don't understand everything in the log files but I can explain a few
things. 1) link.exe is the linker, for MFC and non-MFC programs. MFC is just a 2) The .lib files that are specified in your non-MFC program are for 3) MFC uses a compiler command - #pragma comment(lib, "libname.lib") - 4) The C run time libraries are msvcrt(d).lib, crt(d).lib and one other some is in msvcp60(d).dll or msvcirt(d).dll. Those DLLs don't show up in Most people never look at the log files. I'm sure it can be very Quote:
> question 1: > When I compile my C program with without MFC support. In the build > question 2: > When I compile with MFC support. In the build log file ( test.plg). > "D:\vc\test\unchain.cpp" > thanks . |
|
| Sat, 21 Feb 2004 06:18:06 GMT | |
|
|
|
vc++ compile log
Quote:
> question 1: > When I compile my C program with without MFC support. In the build
Quote:
> I wonder
In the MSDN, search for a function defined in <stdio.h>, say printf(). The> which library contains standard C library ( e.g stdio for example ). > Which library contains standard C++ library? help entry includes this: "Libraries LIBC.LIB Single thread static library, retail version
Quote:
> And in linking step, It shows:
Yes.> ====================================================== > Creating command line "link.exe > ====================================================== > Does VC++ use link.exe to link non-MFC library to form executable?
Quote:
> question 2: > When I compile with MFC support. In the build log file ( test.plg). > "D:\vc\test\unchain.cpp" the "C++" tab. At the bottom of the form you will see a list of all of the command line options passed to the compiler (cl.exe"). To see the link options click the "Link" tab.
Quote:
> where it specific the libraries?
On the "Link" tab choose the "Input" option in the combo box. The list oflibraries appears in the first edit control.
Quote:
> Does VC++ use a different linker other than link.exe to link MFC
No. The IDE creates a make file that invokes cl.exe and link.exe unless you> library to form executable? change it. Regards, |
|
| Sat, 21 Feb 2004 06:40:15 GMT | |
|
|
|
vc++ compile log Will,
But do you mean cl.exe is the vc++ compiler & link.exe is the vc++ thanks again. On Mon, 3 Sep 2001 18:40:15 -0400, "William DePalo [MVP]" Quote:
>> question 1: >> When I compile my C program with without MFC support. In the build >No. Most of them are components of Win32. >> I wonder >In the MSDN, search for a function defined in <stdio.h>, say printf(). The >"Libraries >LIBC.LIB Single thread static library, retail version >> And in linking step, It shows: >Yes. >> question 2: >> When I compile with MFC support. In the build log file ( test.plg). >> "D:\vc\test\unchain.cpp" >Click on the "Settings" item of the "Project" menu in the IDE. Then click >> where it specific the libraries? >On the "Link" tab choose the "Input" option in the combo box. The list of >> Does VC++ use a different linker other than link.exe to link MFC >No. The IDE creates a make file that invokes cl.exe and link.exe unless you >Regards, |
|
| Sat, 21 Feb 2004 08:53:13 GMT | |
|
|
|
vc++ compile log But in directory
C:\Program Files\Microsoft Visual Studio\VC98\Lib I saw : I wonder why not put all object files into library files? I read a what's the file with .PDB extension? Is it same as object file? And in directory: thanks again. On Mon, 03 Sep 2001 15:18:06 -0700, Bruce Dawson Quote:
>I don't understand everything in the log files but I can explain a few >things. >1) link.exe is the linker, for MFC and non-MFC programs. MFC is just a >2) The .lib files that are specified in your non-MFC program are for >3) MFC uses a compiler command - #pragma comment(lib, "libname.lib") - >4) The C run time libraries are msvcrt(d).lib, crt(d).lib and one other >some is in msvcp60(d).dll or msvcirt(d).dll. Those DLLs don't show up in >Most people never look at the log files. I'm sure it can be very
>> question 1: >> When I compile my C program with without MFC support. In the build >> question 2: >> When I compile with MFC support. In the build log file ( test.plg). >> "D:\vc\test\unchain.cpp" >> thanks . |
|
| Sat, 21 Feb 2004 09:04:14 GMT | |
|
|
|
vc++ compile log
Quote:
> But do you mean cl.exe is the vc++ compiler & link.exe is the vc++
What do you mean what do I mean? :-)> linker? Look at the directory \program files\microsoft visual studio\vc98\bin on the disk where you installed VC/C++. You will find several executables. cl.exe ==> compiler These tools can run at the command line. In addition the IDE knows how to
Quote:
> ===========================================
Yes.> And you said: > "In the MSDN, search for a function defined in <stdio.h>, say > printf(). The > help entry includes this: > LIBC.LIB Single thread static library, retail version > LIBCMT.LIB Multithread static library, retail version > MSVCRT.LIB Import library for MSVCRT.DLL, retail version " > ------------------------------- > does the above means u can static link stdio.h functions into ur > executable(LIBC.LIB/LIBCMT.LIB) or dynamic link with MSVCRT.DLL at > runtime? > ===========================================
Quote:
> does c/c++ tab in (project settings) changes complier options & link
Yes.> tab changes linker options?
Quote:
> thanks again.
You are welcome.Regards, |
|
| Sat, 21 Feb 2004 09:45:02 GMT | |
|
|
|
vc++ compile log
Quote:
> I saw :
That is an option but it is always a second step. That is a source file is> 1) object file (.OBJ) (.PDB) > 2) library file (.LIB) > 3) DLL (.DLL) > I wonder why not put all object files into library files? compiled to an object file. One or more object files can be inserted into a library.
Quote:
> I read a book said if you link with an object file. you will include
That's true. But if, for example, the function foo() lives in foo.obj and ifeverything > into exectable. While if link with library file. you look up a > function in libaray and only include specific function into > executable. foo.obj is inserted into foo.lib, and if you need to call foo() in your program, the linker will add it in either case. It hardly matters where it came from. Libraries are most useful for collecting a set of related objects into a
Quote:
> what's the file with .PDB extension? Is it same as object file?
That's the program data base. It contains debug information. It is not anobject file.
Quote:
> And in directory:
Yup.> C:\Program Files\Microsoft Visual Studio\VC98\MFC\SRC > are those MFC source code? Regards, |
|