From: "Aaron Ardiri" <[EMAIL PROTECTED]> > > ...and then the errors get really, really wierd. (This > > did compile with -palmos3.5, really, I swear.) > > if it compiles with 3.5, then - why dont you just use sdk3.5? there > is no reason for you to compile against palmos 3.0 sdk's. the topic > has been discussed a lot on the forums before - search the archives. > Or, to put it another way, the version numbers on the SDK don't indicate what PalmOS version they target, but the highest PalmOS version they support. In general you can (and should) use the most recent SDK available to target the PalmOS versions you're interested in.
In order to make your code run under PalmOS 3.0 you should make sure that you're only calling routines that work in PalmOS 3.0. If you do this using the 5.0 SDK your app will run on all versions of the OS from 3.0 upwards (with the previso below). A more difficult issue is that from one major version to another certain behaviours alter. An example in the 3.0 to 3.5 step is changes to the way forms are drawn and changes to the serial APIs. You therefore have to test carefully under all PalmOS versions you want to support and sometimes code differently than you would if only running on later PalmOS versions. For details, as Aaron says, search the archives. You will also find that some functions are documented as being supported in version x but that they don't actually work until version x+1. Unfortunately PalmSource still, to my knowledge, don't document these problems anywhere so, again, use the forum archives. Chris Tutty -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
