[EMAIL PROTECTED] wrote:
> 1) Which is the first OS version that will be require a different compile
> for each CPU?
If there is one, it's off in the distant future. Certainly Palm OS 5
will not require this.
As became clear last week at PalmSource, the build process for most apps
won't change at all on Palm OS 5. You'll still be building M68K apps,
and they'll be run under emulation on ARM devices. This was demonstrated
again at PalmSource, and the performance is perfectly acceptable (i.e.,
better than current devices).
> 2) Will I have to switch to Code Warrior to develop for this new version
> (OS 5.0)? OS 4.0?
Absolutely not. PRC-Tools works well with 4.0 (which is the current
extant M68K version of Palm OS) currently, and, as described above, for
the most part nothing relevant changes with 5.0: you build your app
just the same way as you would for a current M68K device.
> OR, does (or will) GCC and PRC-Tools currently work
> with these?
Yes, prc-tools currently works with these.
Applications running on 5.0 on ARM devices may include small subroutines
as native ARM code if they need blazing performance. Such applications
can be built with prc-tools today. (If you build prc-tools yourself;
binary prc-tools releases do not yet provide this functionality.) See
this article for details:
http://falch.net/Articles/?art=311
> 3) Say I have an application that was compiled for OS 3.5, which is the
> first OS version that this application will fail to run on, if any?
PalmSource have said that the M68K emulation layer ("PACE") will be
supported for quite some time. So this is even further off in the
distant future than your question 1.
(Assuming that your application is well-behaved, uses the APIs, etc etc.)
John
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
