> > hmm.. CW -> gcc is a piece of cake in comparison to the other way
> > around :) gcc -> CW is a nightmare, as you need to recreate all the
> > resources in constructor and get the resource #defines correct :)
>
> gcc -> CW porting is fairly easy when using the PilRC plugin, as you
> should know, Aaron.
of course, however, i have found it easier to actually use pilrc
to generate the resource files, use prc2pilrc to get the (x,y)
offsets for each object in the forms.. and then enter it into
constructor and generate the header file for the resources.
constructor has a special way of doing its #defines - so i use
that as the basis for the .rcp constants and the development is
seamless, share the .c files between codewarrior and prc-tools
builds.. its quite nice once it all works :P
PilRC plugin works wonders too - however, when writing sample
apps, its not nice to say "screw constructor, use pilrc plugin" :)
// az
[EMAIL PROTECTED]
http://www.ardiri.com/ <--- free games!
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
