How will you know what components are in my CE image?
This is how ceconfig.h file comes in handy. This file list all the components that are included with your CE image. In cases where an application may run well on one system(say x86) but when moved to other system(say SH4) it just won't work. The possible cause for this issue might be that the BSP provided for the SH4 system lacks a few components which were available in the x86 system. To verify this, you can compare the ceconfigs used on both system and you should be able to find a hint from it.Here's a snapshot of this file:
#ifndef __CECONFIG_H__
#define __CECONFIG_H__
// CEFilter Component List:
#define CE_MODULES_COREDLL 1
#define CE_MODULES_KCOREDLL 1
#define CE_MODULES_NK 1
#define CE_MODULES_NKLOADER 1
#define CE_MODULES_OEM 1
#define CE_MODULES_OALIOCTL 1
#define CE_MODULES_FPCRT 1
#define CE_MODULES_CONSOLE 1
#define CE_MODULES_CMD 1
#define CE_MODULES_COMMCTRL 1
#define CE_MODULES_COMMDLG 1
#define CE_MODULES_SHELL 1
#define CE_MODULES_LOADDBG 1
#define CE_MODULES_SHELLCELOG 1
2 comments:
How did you find out about the usage of ceconfig.h ? I couldnt find any references to its definition/purpose on MSDN ?
Actually, the ceconfig.h is the file read by the WinCE Run-time License Assesment Tool as it list all the catalogs/components the current image is using. You can use either keywords and search in MSDN.
Post a Comment