Precautions for developing Device Drivers in Visual C ++

Precautions for developing Device Drivers in Visual C ++

To put it simply, the process of using the makefile project to create a device driver is to call the DDK command in Visual C ++. The execution sequence of the command window is the same as that of the DDK Command Prompt window, the executable files of the driver are also stored in the same directory. The difference between them is a command prompt window in the DDK, and a command is called in the integrated development environment of Visual C ++. However, it is different from developing Win32 using Visual C ++. It does not have window messages and messages to be processed, nor can it compile a single original code file, the executable file cannot be directly run.

In short, when using the makefile project to develop device drivers, pay attention to the following points:

1. When adding or deleting files to or from the makefile project, you must modify the total sources macro of the corresponding sources file so that the build tool can correctly identify the driver source files to be compiled and connected.

2. To generate source code browsing information, you must add the following statement to the sources file:

Brouse_info = 1

3. You cannot compile a single driver source file in the makefile project or directly run the executable file, that is, the "build compile XXX" and "build/execute" menu items of Visual C ++ cannot be executed. At the same time, Visual C ++ cannot be used for debugging because they all belong to system kernel mode components.

4 in Windows 98, when the project configuration is changed from "Win32 free" to "Win32 checked", the "build/rebuild all" menu item of Visual C ++ should be executed in the Empire, all driver source files have been re-compiled. When this happens in Windows 2000, you do not need to create a new one.