Could you just use #ifdef/#ifndef? It seems that each new version of
the SDK includes a few new symbols. Could you use something like,
if <some 2.0 function does not exist> 1.x
else if <some 3.0 function does not exist> 2.x
else if <some 3.x ....
Or, you could create one define at the top of your code (or a symbol in
your make file) that the user has to set. Basically, I AM BUILDING
WITH... and then use #ifdef's in your code to build properly.
The later might work better since the headers even changed names with
3.5.
Good Luck
-jjf
-----Original Message-----
From: Chris Faherty [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, March 07, 2000 7:50 AM
To: Palm Developer Forum
Subject: Re: How to determine PalmOS header version
On 07-Mar-00 Roger Chaplin wrote:
> Why not just edit the PalmOS.h files in the various SDKs to add your
> own SDK version #define? True, your source code would then not compile
> against a "standard" SDK. You have to weigh the pros and cons for
> yourself.
It's not just for me per se. I write free software and I want it to
compile
easily on various SDK, and it has been a problem in the past because I
still
often encounter the PalmOS2 headers in some places and PalmOS3 in
others.
i.e. different contributors to a project.
In other words, it would be nice if it "just worked" and users could
build
the project regardless of SDK version (assuming I don't use newer
features
etc).
/* Chris Faherty <[EMAIL PROTECTED]> */
--
For information on using the Palm Developer Forums, or to unsubscribe,
please see http://www.palm.com/devzone/mailinglists.html
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palm.com/devzone/mailinglists.html
