Why CAB's for MIPS, SH3 in PocketPC-Project?

[Guest]

Hello NG!

If you create a project for 'intelligent devices' and define PocketPC as
target-os, then the application only runs under PPC, right? I mean it won't
work with WinCE-systems (where I'm not clear, what's the difference, because
PPC also is WinCE?). If I collect my knowledge, then PPC is a special
'build' of the WinCE-Kernels, right?


But as far as I know PPC-device are always ARM (or StrangArm or XScale). Why
VS creates CAB-files for MIPS and SH3 by default. In my opinion they are
never used. BTW, how popular are these processors? Does someone know some
devices using that processors?

I'm also not clear, how to use a WinCE-application on a PPC. The default
window-size is much to large for a PPC. Or do I have to take the limits of a
PPC as the maximum border-size for forms in this case?

I would be pleased if there's someone who can help me to clear my
confusion...

Thanks, D.Barisch

 

[Peter Foot [MVP]]

Pocket PC 2000 devices (which are still supported by .NETCF) ran on a number
of processor types - SH3, MIPS and ARM, from Pocket PC 2002 all devices have
been based on ARM processors.
It is possible to create an application which will adapt to the screen-size
of a Pocket PC or Windows CE device at runtime, if you intend the
application to run on both then hard-coding your UI would be impractical.
This means a lot of code needs to be added to setup the form for the
available screen-size which cannot be done using the designers.
Another option is to put all your application logic into a class-library
project and create separate applications for Pocket PC and Windows CE.NET
configurations - these projects only need to have unique forms and can call
into the common dll for all the functionality.

Peter