The installation procedure is actually rather shorter and simpler than this Web page! Its length is because we've tried to explain the background behind the parts that may be unfamiliar.
You need to decide where to put your PalmDev tree, i.e., where you will install Palm OS SDKs and other Palm OS-related header files and libraries (collectively, development material). Palm OS programmers tend to spend more time than most studying system header files, so we suggest somewhere easily accessible such as C:\PalmDev. (Create this directory if it doesn't already exist.)
You also have some choices to make with respect to some of the components:
.zip) or not at all (and use the manuals available online);
setup.exe. The easiest way to use it is described here.)
Run Cygwin's setup utility,
setup.exe, which you can obtain
by selecting one of the Install Cygwin now icons on the
Note: If you are using
2.573.2.3 (released in August 2008) or later it will not let you download
prc-tools by default because our
setup.ini package information
file is not signed. Make a shortcut where you specify the command to run
"setup.exe -X". The -X option will force setup to skip the
verification of the cryptograhic signature of our
The various options in setup.exe are mostly self-evident and depend solely on your personal preferences. The ones that do matter are:
http://prc-tools.sourceforge.net/install(The list of available download sites is a multiple selection list box, so you can <Ctrl>-click to select more than one site. The URL might be displayed in the list in an abbreviated form as just http://prc-tools.sourceforge.net even though the full URL has been accepted.
If you get the error message
Unable to get setup.ini from
http://prc-tools[...], check the URL you added and add it again
if necessary. Most people who have encountered this message have eventually
found that it was caused by a mere typo, such as the addition of a trailing
space to the URL.)
In particular, you will want to consider the Palm OS-related packages, which are in the Devel category:
Of these five packages, only prc-tools itself will be installed by default, so if you need the others you will need to go into the Devel category yourself and select them.
You can always add new packages later or update the existing ones: just run
If you have any problems installing or using Cygwin, your first step should
be to check the Cygwin documentation and
Replace C:\PalmDev by wherever you chose to install SDKs (but keep the quote marks to avoid misinterpretation of any backslashes).
mount -tf "C:\PalmDev" /PalmDev
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
(For simplicity of presentation, in the remainder of this section we'll use
C:\PalmDev as an abbreviation for
the directory which you
have chosen to contain your PalmDev tree, typically C:\PalmDev.
If you've chosen a different location, you should make the appropriate
substitution in what follows.)
Palmdev-prep will search C:\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
To work from an ordinary Windows Command Prompt (
DOS window), you
need to add C:\cygwin\bin to your PATH environment variable there.
(Replace C:\cygwin by wherever you chose to place Cygwin's root
directory, of course.)
Depending on your version of Microsoft Windows, you do this in the System control panel (the Environment Variables section of the Advanced tab) or in C:\AUTOEXEC.BAT. You only need to do this once.