有关Windows版本的宏

2007年05月17日 星期四 下午 01:59

在使用一些新版本的API，或者控件的新特性（比如新版的ComCtl32.dll）的时候,你可能会得到“error C2065: undeclared identifier.“这个错误。原因是这些功能是依赖于你的操作系统的版本的。而你的头文件中的定义并不是最新的。（对于MFC,就是stdafx.h）下面这篇MSDN文章介绍了如何解决这个问题，并详细列举了每个Windows版本对应的NTDDI_VERSION，_WIN32_WINNT，WINVER，_WIN32_IE这些宏。

原文：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.

Minimum system requiredMacros to defineWindows VistaNTDDI_VERSION >=NTDDI_LONGHORN Windows Server 2003 SP1NTDDI_VERSION >=NTDDI_WS03SP1Windows Server 2003NTDDI_VERSION >=NTDDI_WS03Windows XP SP2NTDDI_VERSION >=NTDDI_WINXPSP2Windows XP SP1NTDDI_VERSION >=NTDDI_WINXPSP1Windows XPNTDDI_VERSION >=NTDDI_WINXPWindows 2000 SP4NTDDI_VERSION >=NTDDI_WIN2KSP4Windows 2000 SP3NTDDI_VERSION >=NTDDI_WIN2KSP3Windows 2000 SP2NTDDI_VERSION >=NTDDI_WIN2KSP2Windows 2000 SP1NTDDI_VERSION >=NTDDI_WIN2KSP1Windows 2000NTDDI_VERSION >=NTDDI_WIN2K

The following table describes the legacy macros in use by the Windows header files.

Minimum system requiredMacros to defineWindows Vista_WIN32_WINNT>=0x0600
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.