Re: Developing with eVC for PPC and WM 5.0
- From: r_z_aret@xxxxxxxxxxxx
- Date: Mon, 24 Jul 2006 14:03:51 -0500
On 23 Jul 2006 19:45:04 -0700, junk@xxxxxxxxx wrote:
Do you use the same executable (since it is ARM) and simply change the
install stuff (ie, the cab) to mention ARMV4 rather than ARM (or are
compiler changes needed)? When I try to install my app on a WM5 device,
I get the message "CAB was unsuccessful. The installation file is not
intended for this device."
For each of my apps, each CAB file for Pocket PC works on all versions
of Pocket PC from the original (2000) to WM 5. So for each
application, I have 3 CAB files that handle all Pocket PCs running all
CPUs (SH3, MIPS, and ARM). For all other platforms, I have a second
set of CAB files built for HPC Pro.
Installations may run into problems with screen resolution. The
following overlap in content, but provide different details:
I'm suffering from platform-overload: much of this source code is share
by a Palm OS, two Windows, and PPC applications. I'm continually
switching between OSs and IDEs and pretty lame when it comes to Windows
CE, er Pocket PC, er Windows Mobile.
I strictly use eVC++ 3.0 for all of my application development for the
Pocket PC 2002, 2003, and Windows Mobile 5 OS devices. I simply generate a
ARM executable which runs on the different OSes. I write all my code in C
with Native APIs, so I don't use the MFC stuff.
Now, if you want to use some of the newest capabilities of the WM 5 OS,
you'll need to do some tricky stuff or switch to a different Microsoft IDE,
however, if you're simply wanting to run your existing ARM executable on WM
5 it shouldn't require much changing. The biggest thing I've run into, is
the necessity of flushing the registry file cache when writing to the
registry file on the system.
<junk@xxxxxxxxx> wrote in message
I have an application written in eVC 3.0 (MFC) that I want to port to
Windows Mobile 5.0. I need to minimize development time and to continue
to support the Pocket PC platform (I currently only support ARMS
processors on the PPC).
1. Can I continue to use the eVC 3.0 development platform?
2. What changes are needed to run on WM 5.0?
3. Will the changes be backwards compatible (i.e., will the new source
still compile for the PPC or should I branch the source code into two
Any other tips?
Thanks for your insight!
To reply to me, remove the underscores (_) from my email address (and please indicate which newsgroup and message).
Robert E. Zaret, eMVP
20 Park Plaza, Suite 478
Boston, MA 02116
- Prev by Date: DateTimePicker value
- Next by Date: Determining free memory
- Previous by thread: Re: Developing with eVC for PPC and WM 5.0
- Next by thread: Re: Developing with eVC for PPC and WM 5.0