=======================================================================
MICROSOFT (R) FOUNDATION CLASSES
Version 4.2
Source Code ReadMe
=======================================================================
This directory contains the source code to the MFC library.
These files have been included for reference purposes, in
conjunction with the Class Library Reference manual and tutorial.
These files are compiled to form the Microsoft Foundation Classes 4.2
(MFC 4.2). The library may be built in a number of configurations,
character sets (UNICODE or ANSI), and whether or not debugging and
diagnostic aids are to be included in applications which link with
the library.
============================================
1. BUILDING A STATIC LINK LIBRARY VARIANT
============================================
The makefile provided can be used to build the static link library
variants of MFC 4.2. See section 2 for instructions on building
the shared DLL variant. The makefile can be used from either the
MS-DOS command line (in a Windows NT cmd shell) or as an External
Project file in the Microsoft Developer Studio.
To build a library in a particular configuration, use the NMAKE tool
and the makefile which is in this directory. The following arguments
can be given to NMAKE to successfully build a specific library variant.
NMAKE {DEBUG=[0|1]} {BROWSE=[0|1]} {BROWSEONLY={0|1} \
{CODEVIEW=[0|1|2]} {OBJ=path} \
{PLATFORM=INTEL|ALPHA|MIPS|PPC|M68K|MPPC} \
{UNICODE=[0|1]} \
{OPT=<CL command line switches>}
Previous versions of MFC supported MODEL and TARGET options to control the
memory model and to support DOS/CONSOLE mode targetting. These options are
no longer supported (your Win32 console application can still be linked to
the GUI MFC library, NAFXCW[D].LIB).
For example to build default model with browser information in the debug
build use the following settings:
Debug Build: NMAKE DEBUG=1 CODEVIEW=1 BROWSE=1
Release Build: NMAKE DEBUG=0
DEBUG=[0|1]
The "DEBUG" argument specifies whether or not to include diagnostic
support code for the library. This may be 0 (for no diagnostics)
or 1 (for full diagnostics).
CODEVIEW=[0|1]
The "CODEVIEW" argument specifies whether to compile the library with
CodeView information or not. You need to compile the library with
CodeView information if you want to trace into MFC code using the
Visual C++ debugger. You should also compile your application files
with the /Zi option, and link your executable with the /debug:full
and /debugtype:cv options.
Setting CODEVIEW does not affect the DEBUG argument, although the
value of the DEBUG argument does affect the default value of CODEVIEW
(discussed below). A value of 0 indicates that no CodeView
information is to be compiled into the library. A value of 1 indicates
to compile in full CodeView information for all modules of the library.
The default value depends on the setting of the DEBUG argument.
If DEBUG=1, CODEVIEW defaults to 1. If DEBUG=0, CODEVIEW defaults
to 0. The installed libraries have been built with CODEVIEW=1 for
maximum CodeView information.
UNICODE=[0|1]
The "UNICODE" argument specifies whether to create an MBCS
or UNICODE aware library. If UNICODE is set to 1, the UNICODE
variant of the specified library will be built. The default,
UNICODE=0, specifies that an MBCS aware (or ANSI) library is
to be built.
OBJ=[path]
We recommend storing .OBJ files in a separate directory so that you
may compile different versions of the MFC library concurrently.
The "OBJ" argument allows you to specify where these files are stored
during the build process. The directory specified is created and
removed automatically as required. This defaults to a combination
of the target, model, and debug status, preceded by a '$' (i.e. $NWD).
OPT=[switches]
If your library needs to be built with custom compiler switches, then
these may be included in the "OPT" argument. Note that switches need
to be separated by spaces, so when including more than one extra
compiler switch, enclose the whole OPT= argument in double-quotes.
This is an advanced feature; read the makefile and the details on each
of the switches concerned in the Microsoft C/C++ Compiler User Manual
before using this option.
Defaults
The default is:
nmake DEBUG=1 CODEVIEW=1 BROWSE=0 BROWSEONLY=0 UNICODE=0 OBJ=$NWD
To set these options from MS Developer Studio, from the Build menu choose
the Settings menu command and set them in the associated build sections.
=============================
2. BUILDING THE SHARED DLL
=============================
Building the shared DLL is very similar to the static link variants. You
must, however, use the MFCDLL.MAK which is also an External Project file.
To build the shared DLL components that contain the implementation for
OLE and ODBC use MFCOLE.MAK and MFCDB.MAK respectively. These additional
DLLs are required only if your application utilizes the database or
OLE classes.
You must provide a unique name for your DLL(s) and you must provide a DEF
file with a matching name. Typically, you can make a copy of the DEF
files provided in the \msdev\mfc\src\<platform> directory.
Once you rename this DEF file to be the same base name as the DLL you're
building you then need to add the additional exports (if any).
Technical note TN033 explains in detail how to build the shared DLL and
how to build an application that uses the shared DLL.
===============================
3. AFTER BUILDING THE LIBRARY
===============================
Once the library has been built successfully, you may want to delete object
files with:
NMAKE CLEAN OBJ=[path]
Note that if you used the "OBJ" argument while building the library, specify
the same sub directory in the cleanup command.
This will remove all of the temporary .OBJ files created by building the
library, and remove the directory where they were stored.
Always perform a cleanup before building a new variant of the library,
or use different object paths for each variant. Note that the OBJ files
are only necessary during the building process.
===========================================
4. BUILDING AND USING THE BROWSE DATABASE
===========================================
A prebuilt MFC browser database is included on the Visual C++ CD-ROM.
It is located in the same directory as the MFC source files, and can be
accessed by opening <cd-drive>:\MSDEV\MFC\SRC\MFC.BSC. You may want to
build a browse database if you wish to merge the MFC browse information
with your own project or you wish to build a different browse variant than
the one provided (MFC.BSC is the browser database for NAFXCWD.LIB).
The following instructions describe how to build the browse database using
MFC's makefile and how to integrate the resulting .SBR files into your
project.
By building the library with either the BROWSE=1 or BROWSEONLY=1
options you can create the browse database files for the MFC source code.
The output browse file (.BSC) will be placed in the source directory
(this allows the browser to find the source files). The browse
database files share a common naming convention with the libraries.
Usually, it is sufficient to build only one browse database, although
you can build a browse variant for each library variant that MFC
supports. In addition, it is possible to build only the browse database,
instead of building all the object files and library file. To build
the NAFXCWD.BSC file, for example:
NMAKE DEBUG=1 BROWSEONLY=1
The output will be placed in NAFXCWD.BSC (in the MFC source directory).
In addition, all of the SBR files (the individual files, which when combined,
form the .BSC) will be preserved in the OBJ directory (in this case $NWD).
You can add these SBR files to your proje
没有合适的资源?快使用搜索试试~ 我知道了~
VisualC++ 微软MFC 核心类库 Lib.rar
共540个文件
cpp:253个
rc:87个
h:76个
3星 · 超过75%的资源 需积分: 31 29 下载量 140 浏览量
2009-09-13
16:11:13
上传
评论
收藏 7.79MB RAR 举报
温馨提示
VisualC++ 微软MFC 核心类库 Lib.rar VisualC++ 微软MFC 核心类库 Lib.rar VisualC++ 微软MFC 核心类库 Lib.rar
资源推荐
资源详情
资源评论
收起资源包目录
VisualC++ 微软MFC 核心类库 Lib.rar (540个子文件)
PCHMARK.BIN 1B
3DCHECK.BMP 1KB
NTCHECK.BMP 378B
95CHECK.BMP 338B
TRUETYPE.BMP 262B
MINIFWND.BMP 198B
MFCDLL.CLW 4KB
DAOCORE.CPP 132KB
DBCORE.CPP 113KB
WINCORE.CPP 107KB
DBRFX.CPP 89KB
OCCSITE.CPP 88KB
OLESVR1.CPP 75KB
INET.CPP 71KB
OLEVAR.CPP 69KB
WINSPLIT.CPP 63KB
OLECLI1.CPP 60KB
WINFRM.CPP 59KB
VIEWRICH.CPP 56KB
ISAPI.CPP 55KB
CTLCORE.CPP 50KB
OLEDISP1.CPP 44KB
DLGPROP.CPP 40KB
OLECLI2.CPP 40KB
OLEMISC.CPP 39KB
BARTOOL.CPP 39KB
OLEPSET.CPP 38KB
OLEDLGS1.CPP 38KB
CTLPPG.CPP 38KB
CTLPROP.CPP 36KB
OLESVR2.CPP 36KB
DAODFX.CPP 35KB
WINGDI.CPP 33KB
VIEWEDIT.CPP 33KB
WINCTRL2.CPP 33KB
WINMDI.CPP 32KB
VIEWPREV.CPP 30KB
CTLPROPX.CPP 29KB
DOCMGR.CPP 27KB
SOCKCORE.CPP 27KB
PPGFONT.CPP 27KB
VIEWSCRL.CPP 27KB
DCPREV.CPP 26KB
BARCORE.CPP 25KB
OLEDOCOB.CPP 25KB
CTLPSET.CPP 24KB
BARDOCK.CPP 24KB
THRDCORE.CPP 24KB
DOCCORE.CPP 23KB
DLGCORE.CPP 23KB
WINCTRL5.CPP 22KB
WINCTRL3.CPP 22KB
STREX.CPP 22KB
OLEDOC1.CPP 21KB
OLELINK.CPP 21KB
DLLINIT.CPP 21KB
CMDTARG.CPP 21KB
WINMINI.CPP 21KB
OLEDOBJ2.CPP 21KB
TRCKRECT.CPP 21KB
ARCCORE.CPP 20KB
DOCKSTAT.CPP 20KB
VIEWHTML.CPP 20KB
OCCMGR.CPP 19KB
OCCCONT.CPP 19KB
BARSTAT.CPP 19KB
FILECORE.CPP 19KB
PPGCOLOR.CPP 18KB
DLGDATA.CPP 18KB
DAOVIEW.CPP 18KB
OLEIPFRM.CPP 18KB
DOCKCONT.CPP 18KB
OLECLI3.CPP 17KB
STRCORE.CPP 17KB
OLEASMON.CPP 16KB
APPCORE.CPP 16KB
OCCDLG.CPP 16KB
OLECONN.CPP 16KB
CTLINPLC.CPP 16KB
DBVIEW.CPP 16KB
CTLEVENT.CPP 16KB
OLEREG.CPP 15KB
CTLREG.CPP 15KB
OLEFACT.CPP 15KB
OLEDROP2.CPP 14KB
TOOLTIP.CPP 14KB
VIEWCORE.CPP 14KB
OLEDOCCL.CPP 13KB
CTLPBAG.CPP 13KB
OLEUNK.CPP 13KB
OLEDISP2.CPP 13KB
DLGFILE.CPP 12KB
AFXTLS.CPP 12KB
DOCTEMPL.CPP 12KB
OLEDOCVW.CPP 12KB
OLESTRM.CPP 12KB
CTLNOWND.CPP 11KB
WINOCC.CPP 11KB
PPGPICT.CPP 11KB
CTLDATA.CPP 11KB
共 540 条
- 1
- 2
- 3
- 4
- 5
- 6
资源评论
- 江浙菜2012-08-04非常有用的好东西,如果你要处理vc6的代码
tan_kaishuai
- 粉丝: 36
- 资源: 142
上传资源 快速赚钱
- 我的内容管理 展开
- 我的资源 快来上传第一个资源
- 我的收益 登录查看自己的收益
- 我的积分 登录查看自己的积分
- 我的C币 登录后查看C币余额
- 我的收藏
- 我的下载
- 下载帮助
最新资源
- 基于spark和kafka的新闻案例+源代码+文档说明
- greenplum-cc-web-6.2.0-gp6-rhel7-x86-64.7z
- 电机控制霍尔传感器和反电动势的关系分析
- 计算机生产实习:OA后台管理(web前端+Java后端)压缩文件包
- greenplum6.10安装时缺失的fpm包
- 缺陷检测-轻量化PCB表面缺陷检测算法实现-工业视觉+六大缺陷检出-优质项目实战.zip
- JAVA 中的Spring框架介绍包括起源、体系结构、核心部分、特点等
- 2024年小米汽车产业链分析及新品上市全景洞察报告
- 基于Qt和C++实现的偏3D风格的异型窗体界面操作+源码(期末大作业&课设&项目开发)
- 基于yolov8的花卉分类系统,包含训练好的权重和推理代码,GUI界面,支持图片、视频、摄像头输入,支持检测结果导出
资源上传下载、课程学习等过程中有任何疑问或建议,欢迎提出宝贵意见哦~我们会及时处理!
点击此处反馈
安全验证
文档复制为VIP权益,开通VIP直接复制
信息提交成功