Windows Driver Kit (WDK) Build Environment
Updated: June 11, 2009
This paper provides information about the Windows Driver Kit (WDK) build environment. It describes how the tools work to provide developers a better understanding of what occurs when a project is built. With a better understanding of the build process, developers can use the tools more effectively.
This paper is helpful for any developer, beginner to advanced, who writes drivers or test applications for any category of device. This paper assumes that the reader has a general understanding of how to build a driver, but would like more information about what the tools are doing during the build process.
This information applies for the following operating systems:
Windows 7
Windows Server 2008
Windows Vista
Windows Server 2003
Windows XP
Included in this white paper:
| • | WDK Build Tools and Operation | • | Setting Up the Build Environment | | • | How the Build Process Works | | • | Optimizing the Order of Build Tasks |
|
| • | Techniques for Building Drivers | • | Building on a Multiprocessor Machine | | • | Using Custom Build Steps | | • | Code Optimization |
|
| • | Viewing Additional Information about the Build Process | • | Creating a Preprocessed Listing | | • | Viewing Generated Assembly Code | | • | Displaying the Build Environment Configuration | | • | Viewing Verbose Linker Information |
|
| • | Storing Driver Package Files in a Specified Directory | • | New WDK Build Environment Features | | • | Using the Default Separate Build Output Directories | | • | Using Custom Build Output Directories | | • | Summary of Build Output Macros and Parameters |
|
