Arthur
Thu Feb 03 23:07:15 CST 2005
Dear Experts,
I tried following steps to build TaskMan as an exe in WinCE5.0, but failed.
Could you give me your advice?
1) New a platform in "PBWorkspaces\MyPB"
2) New a TaskMan project as WCE Application in "PBWorkspaces\MyPB\TaskMan"
3) Copy source codes from "WINCE500\PUBLIC\WCESHELLFE\OAK\TASKMAN" to
"PBWorkspaces\MyPB\TaskMan"
4) Add source files into the TaskMan project and build this project, but
following syntax errors occur:
4.1) minserver.cpp(42) : fatal error C1083: Cannot open include file:
'shellcb.h': No such file or directory
4.2) minshell.cpp(104) : error C3861: 'TouchCalibrate': identifier not
found, even with argument-dependent lookup
4.3) minshell.cpp(153) : error C3861: 'RegisterTaskBar': identifier not
found, even with argument-dependent lookup
4.4) mintask.cpp(179) : error C3861: 'RegisterTaskBar': identifier not
found, even with argument-dependent lookup
4.5) dst.cpp(26) : fatal error C1083: Cannot open include file:
'explorer.h': No such file or directory
5) Add "\WINCE500\PUBLIC\WCESHELLFE\OAK\INC" as additional include directory
to fix error 4.1
6) Add "#include <pwinuser.h>" in minishell.h to fix error 4.2, 4.3 and 4.4
7) Define macro NODSTSAMPLE to fix error 4.5 (I'm afraid it's not a good way
to define this macro) and then build this project, but following link erros
occur:
7.1) housekp.obj : unresolved external symbol _GetSystemPowerStatusEx
7.2) minserver.obj : unresolved external symbol "int __cdecl
ShellRegisterCallbacks(struct SHELLCALLBACKS *)"
8) Link "\WINCE500\PUBLIC\WCESHELLFE\OAK\LIB\X86\RETAIL\shellcb.lib" to fix
error 7.2
But I can not fix error 7.1. According to MSDN, the function
GetSystemPowerStatusEx() requires Coredll.lib. But Coredll.lib has been
already linked. Could you give me your help?
Thanks & Best Regards,
Arthur
"Yannick Chamming's [eMVP]" <ychammings_nospam@adeset.com>
If you are willing to customize it, you can have 2 way of working :
>
> - Create a new directory in public and copy taskman to it so that it can
> be
> handle at sysgen
> - Copy taskman directory to your specific platform (or osdesign) directory
> and update sources file so that it can be generated directly as an exe.
> You'll have to handle the dependencies towards various lib so that it can
> get built.
>
> 2nd option is easiest to handle than first one, but it won't give you the
> same possibilities as first one (localization automatic handling, etc...)
>
> BR
> Yannick
>
>
> --
> ----------------------------------------------------------------
> Yannick Chamming's (eMVP)
> ADENEO (ADESET)
> Windows Embedded Manager
> ychammings AT adeset DOT com>
>
http://www.adeset.com
> Tél : +33 (0)4.72.18.57.77
> Fax : +33 (0)4.72.18.57.78
> ----------------------------------------------------------------
>
> "Dean Ramsier" <ramsiernospam@nospam.com> wrote in message
> news:uZrcNKTCFHA.1932@TK2MSFTNGP14.phx.gbl...
>> It's done at sysgen time
>>
>> --
>> Dean Ramsier - eMVP
>>
>>
>> "Arthur Jiang" <Arthur.Jiang@wadin.com> wrote in message
>> news:uSTGWdOCFHA.3908@TK2MSFTNGP12.phx.gbl...
>> > Dear Experts,
>> >
>> > In file "WINCE420\PUBLIC\WCESHELLFE\OAK\TASKMAN\sources", the TaskMan
>> codes
>> > are specified to generated as an library. But in the release directory,
>> > "taskman.exe" will be generated if I build a platform with TaskMan
> shell.
>> > How does PB to achieve it? How to build TaskMan codes as an exe file
>> > manually?
>> >
>> > Thanks & Best Regards,
>> > Arthur
>> >
>> >
>>
>>
>
>