有关Windows版本的宏
来源:互联网 发布:淘宝开店快递怎么弄 编辑:程序博客网 时间:2024/05/19 20:38
有关Windows版本的宏
原文:http://msdn2.microsoft.com/en-us/library/aa383745.aspx
标题:Using the Windows Headers
The header files for the Windows API enable you to create 32- and 64-bit applications. They include declarations for both Unicode and ANSI versions of the API. For more information, see Unicode in the Windows API. They use data types that allow you to build both 32- and 64-bit versions of your application from a single source code base. For more information, see Getting Ready for 64-bit Windows. Additional features include Header Annotations and STRICT Type Checking.
Microsoft Visual C++ includes copies of the Windows header files that were current at the time Visual C++ was released. Therefore, if you install updated header files from an SDK, you may end up with multiple versions of the Windows header files on your computer. If you do not ensure that you are using the latest version of the SDK header files, you will receive the following error code when compiling code that uses features that were introduced after Visual C++ was released: error C2065: undeclared identifier.
Conditional Declarations
Certain functions that depend on a particular version of Windows are declared using conditional code. This enables you to use the compiler to detect whether your application uses functions that are not supported on its target version(s) of Windows. To compile an application that uses these functions, you must define the appropriate macros. Otherwise, you will receive the C2065 error message.
The Windows header files use macros to indicate which versions of Windows support many programming elements. Therefore, you must define these macros to use new functionality introduced in each major operating system release. (Individual header files may use different macros; therefore, if compilation problems occur, check the header file that contains the definition for conditional definitions.) For more information, see Sdkddkver.h.
The following table describes the preferred macros in use by the Windows header files.
The following table describes the legacy macros in use by the Windows header files.
WINVER>=0x0600 Windows Server 2003_WIN32_WINNT>=0x0502
WINVER>=0x0502 Windows XP_WIN32_WINNT>=0x0501
WINVER>=0x0501 Windows 2000_WIN32_WINNT>=0x0500
WINVER>=0x0500 Windows NT 4.0_WIN32_WINNT>=0x0400
WINVER>=0x0400 Windows Me_WIN32_WINDOWS=0x0500
WINVER>=0x0500 Windows 98_WIN32_WINDOWS>=0x0410
WINVER>=0x0410 Windows 95_WIN32_WINDOWS>=0x0400
WINVER>=0x0400 Internet Explorer 7.0_WIN32_IE>=0x0700Internet Explorer 6.0 SP2_WIN32_IE>=0x0603Internet Explorer 6.0 SP1_WIN32_IE>=0x0601Internet Explorer 6.0_WIN32_IE>=0x0600Internet Explorer 5.5_WIN32_IE>=0x0550Internet Explorer 5.01_WIN32_IE>=0x0501Internet Explorer 5.0, 5.0a, 5.0b_WIN32_IE>=0x0500Internet Explorer 4.01_WIN32_IE>=0x0401Internet Explorer 4.0_WIN32_IE>=0x0400Internet Explorer 3.0, 3.01, 3.02_WIN32_IE>=0x0300
Note that some features introduced in the latest version of Windows may be added to a service pack for a previous version of Windows. Therefore, to target a service pack, you may need to define _WIN32_WINNT with the value for the next major operating system release. For example, the GetDllDirectory function was introduced in Windows Server 2003 and is conditionally defined if _WIN32_WINNT is 0x0502 or greater. This function was also added to Windows XP SP1. Therefore, if you were to define _WIN32_WINNT 0x0501 to target Windows XP, you would miss features that are defined in Windows XP SP1.
You can define these symbols by using the #define statement in each source file, or by specifying the /D compiler option supported by Visual C++. To specify compiler options, go to the Projects menu and click Properties. Go to Configuration Properties, then C++, then Command Line. Enter the option under Additional Options.
Faster Builds with Smaller Header Files
You can reduce the size of the Windows header files by excluding some of the less common API declarations as follows:
- Define WIN32_LEAN_AND_MEAN to exclude APIs such as Cryptography, DDE, RPC, Shell, and Windows Sockets.
- Define one or more of the NOapi symbols to exclude the API. For example, NOCOMM excludes the serial communication API. For a list of support NOapi symbols, see Windows.h
例:
// 或是经常使用但不常更改的
// 项目特定的包含文件
#pragma once
#ifndef VC_EXTRALEAN
#define VC_EXTRALEAN// 从 Windows 标头中排除不常使用的资料
#endif
// 如果您必须使用下列所指定的平台之前的平台,则修改下面的定义。
// 有关不同平台的相应值的最新信息,请参考 MSDN。
#ifndef WINVER// 允许使用 Windows 95 和 Windows NT 4 或更高版本的特定功能。
#define WINVER 0x0500//为 Windows98 和 Windows 2000 及更新版本改变为适当的值。
#endif
#ifndef _WIN32_WINNT// 允许使用 Windows NT 4 或更高版本的特定功能。
#define _WIN32_WINNT 0x0500//为 Windows98 和 Windows 2000 及更新版本改变为适当的值。
#endif
#ifndef _WIN32_WINDOWS// 允许使用 Windows 98 或更高版本的特定功能。
#define _WIN32_WINDOWS 0x0410 //为 Windows Me 及更新版本改变为适当的值。
#endif
#ifndef _WIN32_IE// 允许使用 IE 4.0 或更高版本的特定功能。
#define _WIN32_IE 0x0400//为 IE 5.0 及更新版本改变为适当的值。
#endif
#define _ATL_CSTRING_EXPLICIT_CONSTRUCTORS// 某些 CString 构造函数将是显式的
// 关闭 MFC 对某些常见但经常被安全忽略的警告消息的隐藏
#define _AFX_ALL_WARNINGS
#include <afxwin.h> // MFC 核心和标准组件
#include <afxext.h> // MFC 扩展
#include <afxdisp.h> // MFC 自动化类
#include <afxdtctl.h>// Internet Explorer 4 公共控件的 MFC 支持
#ifndef _AFX_NO_AFXCMN_SUPPORT
#include <afxcmn.h>// Windows 公共控件的 MFC 支持
#endif // _AFX_NO_AFXCMN_SUPPORT
- 有关Windows版本的宏
- 有关Windows版本的宏
- 有关Windows版本的宏
- 有关Windows版本的宏
- 有关windows的多线程
- 进程有关的windows api
- 有关检测浏览器的版本的代码
- Android 编译有关gcc版本的问题
- 有关unity版本对oculus的影响
- 初学者有关Hadoop版本选择的考虑
- 有关于caffe版本的介绍
- Windows的版本定义
- Windows 2000的版本
- Windows ce的版本
- Windows 2003的版本
- Windows NT的版本
- sdk的windows版本
- windows版本的getopt
- 软件开发方法——快速原型模型
- 以后就在这里安家了……
- error C2018: unknown character '0xa1' 错误的解决方法
- 求职面试时常被问到的65个问题与技巧性回答
- C#调用Oracle存储过程并返回结果集
- 有关Windows版本的宏
- VC++下使用ADO编写数据库程序
- 面向对象与基于对象
- Install fctix
- 理解离散傅立叶变换
- 设置数据库兼容级别的两种方法
- 有点迷茫了...
- 旅行售货员问题
- 分页存储过程