This section describes the steps required to implement minimal DirectDraw HAL functionality in your display driver. This section assumes that you do not wish to move an existing DirectDraw HAL from desktop Windows to Windows CE. For information on doing that, please see the chapter, Porting your DDHAL from the Desktop.

Before you continue, you will need the following items to implement a simple DDHAL in your display driver:

• The contents of the DDGPE package (the basic HAL source code).
• The sample display driver package.
• The build files used to export functions from your compiled code (this usually has the name of your compiled binary, as defined in the TARGETNAME=BINARYNAMEsection of your sources file, and ends with the .def extension).
• The build files used to define include paths, and to attach source code and libraries to your project (usually called sources).

  First, modify the file used to export functions from your compiled binary. It should export the HALInitfunction. You can consult the sample driver source code file DDI.def to see how this is done. The HALInitfunction is part of the ddgpe.lib, which you should have already linked to your project.

  Next, modify your include path to include drive:\wince212\public\directX\oak\inc. This should be the path to the following file:

  • DDHFuncs.h

    This is a public header file that can be used by any display driver and should not be modified.

    Copy the following header file from the basic HAL source code into an appropriate location inside your display driver's build directory:

    • GPEHALUsr.h

      This header file is private to your display driver, and can be modified to contain whatever you like. You must customize this file to implement the IN_VBLANKand IS_BUSYmacros, since they are required by the sample DDHAL implementation.

      Now copy the following source code files from the basic HAL source code from the sample display drivers into your display driver's build directory, and add them to the appropriate build files:

      • HalCaps.cpp
      • HalDD.cpp
      • HalSurf.cpp
      • HalPalette.cpp
      • Use the sample display driver that most closely matches the architecture of your display driver.

        Finally, compile and build your display driver and ensure that it continues to work properly. Once you have verified that it is still functional, your driver is ready to be tested with DirectDraw programs. Keep in mind that the code is not in an optimized state, and will require some customization to improve performance. See Taking Advantage of DDGPE, and Customizing Your DDHAL, for more information.

        
        

        ---

         Last updated on Tuesday, July 13, 2004

        © 2004 Microsoft Corporation. All rights reserved.