Migrating the Keyboard PDD Without Conforming to the Layout Manager Interface (Windows CE 5.0)
The keyboard platform dependent driver (PDD) is the hardware-dependent code of the keyboard driver. When you migrate a keyboard driver without conforming to the Layout Manager interface, build the keyboard PDD before building the entire keyboard driver.
To migrate the keyboard driver PDD
Copy your Windows CE .NET 4.1 or earlier keyboard driver to your Windows CE .NET 4.2 or later keyboard driver's directory.
For example, copy the contents of %_WINCEROOT%\Platform\Emulator\Drivers\KbdMouse to the %_WINCEROOT%\Platform\Emulator\Drivers\MyKbdMouse directory in the latest Platform Builder installation.
In the latest Platform Builder installation, in %_WINCEROOT%\Platform\%_TGTPLAT%\Drivers, open the dirs file.
Update the keyboard driver section of the dirs file to specify Mykbdmouse instead of Kbdmouse.
This action preserves the installed keyboard driver.
In your Windows CE .NET 4.2 or later keyboard driver directory, create a new directory, and name the directory Inc.
The keyboard driver directory is the directory immediately subordinate to the Drivers directory for the hardware platform. For example, %_WINCEROOT%\Platform\Emulator\Drivers\Kbdmouse is the keyboard driver directory for the Emulator BSP.
From your Windows CE .NET 4.1 or earlier source tree, copy %_WINCEROOT%\Public\Common\OAK\Inc\Keybddr.h and %_WINCEROOT%\Public\Common\OAK\Inc\Keybdpdd.h to the Inc directory in the latest Platform Builder installation.
In the sources file for the Windows CE .NET 4.2 or later keyboard driver PDD that was copied over in step 1, add the Inc directory to the list of directories specified by the INCLUDES macro definition.
You might have to add a new INCLUDES macro definition to the sources file. For information about modifying the Sources file, see Sources File and INCLUDES.
See Also
How-to Topics | Layout Manager
Send Feedback on this topic to the authors