Migrating the Keyboard DLL Without Conforming to the Layout Manager Interface (Windows CE 5.0)
In the process of migrating a keyboard driver without conforming to the Layout Manager Interface, migrate the entire dynamic-link library (DLL) after you migrate the keyboard PDD. The sources files responsible for building the keyboard DLLs typically reside in %_WINCEROOT%\Platform\%_TGTPLAT%\Drivers\Kbdmouse\DLL.
To migrate the keyboard DLL without conforming to the Layout Manager Interface
From your Windows CE .NET 4.1 or earlier source tree, copy %_WINCEROOT%\Public\Common\OAK\Inc\Kbdmouse.def to the Inc directory you created previously.
In the subdirectories of the DLL directory, which is immediately subordinate to the keyboard driver directory, update the sources files to use the .def file that now resides in your keyboard driver's Inc directory.
These sources files build your keyboard driver DLLs. For example, the Emulator DLL directory is %_WINCEROOT%\Platform\Emulator\Drivers\Kbdmouse\DLL. For information about configuring this sources file, see Sources File and DEFFILE.
From the keyboard driver directory for your hardware platform, build the keyboard driver DLLs.
An example of a hardware platform's keyboard driver directory is %_WINCEROOT%\Platform\Emulator\Drivers\Kbdmouse.
For information about building the keyboard driver, see Build Tool.
View the keyboard driver DLLs build errors.
The build errors expose the Windows CE .NET 4.1 or earlier library (.lib) files to copy and build in your Windows CE .NET 4.2 or later keyboard driver.
Depending on the .lib file errors in the keyboard driver DLLs build log, you might have to copy one or more directories from the Windows CE .NET 4.1 or earlier source tree to your Windows CE .NET 4.2 or later keyboard driver directory.
For example, if you receive an error stating that Kbdist.lib cannot be found, copy %_WINCEROOT%\Public\Common\OAK\Drivers\Keybd\IST from Windows CE .NET 4.1 or earlier to Windows CE .NET 4.2 or later. You might have to copy one or more of the following directories from the Windows CE .NET 4.1 or earlier source tree to your Windows CE .NET 4.2 or later keyboard driver directory:
- %_WINCEROOT%\Public\Common\OAK\Drivers\Keybd\IST
- %_WINCEROOT%\Public\Common\OAK\Drivers\Keybd\ScanVK
- %_WINCEROOT%\Public\Common\OAK\Drivers\Keybd\VKChar
- %_WINCEROOT%\Public\Common\OAK\Drivers\Keybd\VKRemap
After copying the IST, ScanVK, VKChar, or VKRemap directories to your Windows CE .NET 4.2 or later keyboard driver directory, add these directories to the keyboard driver dirs file and list the DLL directory last in the dirs file.
For information about Dirs files, see Dirs File.
For any sources files that you copied from the Windows CE .NET 4.1 or earlier source tree to the Windows CE .NET 4.2 or later %_WINCEROOT%\Platform\Emulator\Drivers\Kbdmouse directory, add the Inc directory to the list of directories specified by the INCLUDES macro definition.
You might have to add new INCLUDES macro definitions to the sources files. For information about the INCLUDES macro definition, see INCLUDES.
Note For the Windows CE .NET 4.1 or earlier keyboard driver, the .lib files reside in a subdirectory of _COMMONOAKROOT. However, after copying the directories from Windows CE .NET 4.1 or earlier and executing Build.exe, the .lib files might reside in a different location.
For the directories you copied from the Windows CE .NET 4.1 or earlier source tree, in the keyboard driver DLL sources files, update the SOURCELIBS paths to specify a subdirectory of _PROJECTOAKROOT, instead of _COMMONOAKROOT.
For example, if you copied the ScanVK directory from Windows CE .NET 4.1 or earlier, in the %_WINCEROOT%\Platform\Emulator\Drivers\Kbdmouse\DLL\KBDEMULXTMSENGUS1 sources file, change the location of the ScVkXTMsEngUs1.lib file from _COMMONOAKROOT to _PROJECTOAKROOT. _COMMONOAKROOT specifies the directory where the .lib files built from the Public branch of the source tree are stored. _PROJECTOAKROOT specifies the directory where the .lib files built for your hardware platform are stored.
For information about sources files and the SOURCELIBS macro definition, see Sources File and SOURCELIBS.
See Also
How-to Topics | Layout Manager
Send Feedback on this topic to the authors