To install a prc-tools RPM, download the appropriate version and architecture from the downloads page and install it using your favourite package management tool, or by logging on as root and typing
# rpm -Uvh prc-tools-version
Most of the other components used in conjunction with prc-tools are also available as RPMs:
Unix installer(listed first on the page, as Palm OS SDK 4.0 for CodeWarrior and/or PRC-Tools) is a tarball containing an RPM and its license.
Earlier versions of the SDK and other Palm OS-related SDKs are not available as RPMs; you'll have to install them in /opt/palmdev/sdk-n manually.
You'll need to download ROMs from the usual places separately and install them manually: they are generally not redistributable, so only PalmSource itself (or, generally, the copyright holder for a particular ROM) could distribute them packaged as RPMs.
The tools RPMs (but not the SDK ones) are listed in the Development/Palm OS group at rpmfind (but not at all mirrors).
m68k-palmos-gccwill be able to find Palm OS-related headers and libraries automatically, i.e., without needing any extra
-Loptions, and will have a new
-palmosN option for selecting which SDK to use.
You should rerun palmdev-prep whenever you upgrade prc-tools or install or
remove a Palm OS SDK or other development material. You should also rerun
it using its
-d SDK option when you want to change
which SDK is to be used by default, i.e., in the absence of any
Because it creates configuration files in system directories, this too needs to be done while you are logged on as root:
Palmdev-prep will search /opt/palmdev for SDKs and other development
material and report on what it finds.
This report reflects the SDKs that will be accessible via a
option to GCC, so if it fails to list some SDK that you think you have
installed, you'll have to figure out why prc-tools has not been able to
detect it. In general, prc-tools prefers and expects the directory structure
of a Palm OS SDK to look like
For compatibility with some of the ways in which SDKs have been packaged, palmdev-prep will also correctly detect an SDK when header files are under
- Header files, arranged in arbitrary directories under include
- Static (link-time) libraries for m68k-palmos
includeand/or libraries are under
GCC Librariesinstead of
In the past, /usr/local/palmdev was the canonical place to put SDKs. If you still have SDKs installed there, you can either move them or tell palmdev-prep to look there as well each time you run it:
# palmdev-prep /usr/local/palmdev