>> I've just started doing some palm OS 5 development with code warrior
>> 4.04, however I'd like to be able to drive the build process directly from
>> the command line, without using the IDE and without using .mcp files
>> (basically, without using code warrior).
>> I can, of course, call armcc from the command line to generate a .axf
>> file, I'm just not sure what code warrior is doing to create the .prc,
>> and the process doesn't appear to be documented as the SDK assumes
>> code warrior will be used. Is there any way to get code warrior to
>> tell you exactly what it is doing at each stage of the build, or any
>> other way of finding this out?
> What tools are you using? Palm OS 5 development uses the 68K toolset
> included in CodeWarrior for Palm OS V8. We don't supply an ARM compiler
> for Palm OS targets yet.
> Note: ARM Ltd. sells an embedded toolset built around the CodeWarrior
> IDE. I think the ADM SDT 2.5 uses IDE 4.0.4, which is where you're
> getting the version confusion.
This is indeed the version of CodeWarrior that I'm using, with a
plugin SDK for Palm OS 5 running on an Xscale development board.
Quote:> I understand that PalmSource and many licensees are using this
> toolset to build their Palm OS 5 configurations, but on OS 5, PRC
> files are still 68K based, although they can contain ARM code
Well, the demos supplied with the SDK build OK, and I don't have a 68K
compiler installed. CodeWarrior builds an ARM axf image as it would
if I was building for any other ARM target and then works some magic
to generate a prc, it's what process it's going through to do this
that I can't quite follow. Is there no way of making CodeWarrior
display exactly what it's doing when it calls an external tool?
Quote:> BTW, our 68K tools are not usable from the command line, other than
> invoking the IDE from the command shell to build a project. We're
> working on this for a future release, but the current problem is that we
> only have the PalmRez Post-Linker in IDE plugin form.
I understood there to be a problem with PalmRez from looking at the
group archives on google, However looking at the Target Settings for
the supplied demo programs I see that it's using PalmPRC PostLinker as
the Post-linker, PalmRez doesn't seem to be involved in the build
Thanks for your help,