PALM PROGRAMMING: The Software Development Kit (SDK)



The SDK is provided by Palm OS as a library plus header files for program development. It is essential, as only it 'knows' how to write to the palm lcd, or respond to a button push. It IS the application programming interface. You make requests of the sdk library, to check for buttons, print on screen, etc.

Step 1:

http://www.palmos.com/dev/tech/tools/sdk40.cgi

download the sdk40.tar.gz

while you're there

http://www.palmos.com/dev/tech/tools


Download

sdk40-docs.tar.gz #doc
sdk40-examples.tar.gz #examples

Unpack these two and save for a rainy day. You *will* use them.


Step 2:

unpack the sdk tarball.

unusually, it will extract an rpm file plus some blurb.

simply install the rpm via kpackage, or,

rpm -ivh sdk40.rpm.noarch.rpm


Step 3:


EVERYTHING in these steps rely on /usr/local/palmdev


Rather than me entering a religious war of no benefit, suffice to say, that the sdk, the pilrc, and others have changed their minds over where to put things on succeeding releases. Each tells you about the other and how to make them all 'compatible'

My defintion of compatible is to place them all treed in /usr/local/palmdev, and indeed, the majority of readme's keep referring to it.

The sdk rpm will extract to /opt/palmdev/sdk-4

Simply move it to /usr/local/palmdev

(There is an rpm --switch to do just that, but I have explained the longhand to be informative)

Step 4: Tidy symlink

For the resource compiler, and the general compiler (prctools) to 'work' it needs to find /usr/local/palmdev/sdk

as a result

cd /usr/local/palmdev
ln -s sdk-4 sdk

Voila.

Next -> The  PalmOS compiler (prctools)


searchSearch Index