Why do I get errors like "/Program not found"?
The installation instructions are built assuming that you are running an
english version of Microsoft Windows and that the directory names used in
the environment variables (the shorthand versions) map the the correct
directories:
C:\Progra~1 --> C:\Program Files\
It may be possible that the "C:\Progra~1" directory name does
not actually map to the correct directory. This type of directory name is
that which does not require any spaces and confirms to the 8.3 MSDOS
style directory naming system. You should manually test these names, as it is
possible that there may be other directories. For example, one user
reported the following:
C:\Progra~1 --> C:\Programme\
C:\Progra~2 --> C:\Program Files\
In this case, replacing "C:\Progra~1" with "C:\Progra~2"
solved the problem.
How do I make sdk x.x the default sdk?
PRC-Tools will use the sdk that is specified as an argument to the compiling
utilties (like -palmos2). In the case where no sdk is specified, the
compilers look for a default sdk. You can set the default sdk by doing the
following in the bash prompt:
$ cd /Program\ Files/GNU\ PalmPilot/sdk
$ rm -rf sdk
$ ln -s sdk-3.5 sdk
$ ls -l
total 1
drwxr-xr-x 3 544 everyone 0 Nov 5 13:42 doc
drwxr-xr-x 2 544 everyone 0 Nov 5 13:42 include
drwxr-xr-x 3 544 everyone 0 Oct 1 16:04 lib
drwxr-xr-x 6 544 everyone 0 Oct 1 16:05 samples
lrw-r--r-- 1 544 everyone 18 Nov 6 00:02 sdk -> sdk-3.5
drwxr-xr-x 3 544 everyone 0 Oct 1 16:05 sdk-1
drwxr-xr-x 3 544 everyone 0 Oct 1 16:06 sdk-2
drwxr-xr-x 3 544 everyone 0 Oct 1 16:06 sdk-3.1
drwxr-xr-x 4 544 everyone 0 Oct 1 16:05 sdk-3.5
$
A symbolic link has been created such that accessing the "sdk"
directory will now redirect the system to the "sdk-3.5" directory
(palmos 3.5 sdk is now the default).
I installed the sdk's, but the compiler cannot find them.
PRC-Tools keeps track of where to find the sdk my using a mount point that
is stored in the system registry. You can check what these are by doing the
following at the bash prompt:
$ mount
Device Directory Type Flags
C:\Program Files\GNU PalmPilot\prc-tools /prc-tools native text!=binary
C:\Program Files\GNU PalmPilot\sdk /PalmDev native text!=binary
C: / native text!=binary
The /PalmDev mount point is the one that informs the compiler
where the sdk's are located.
$ mount C: /
$ mount C:\\Program\ Files\\GNU\ PalmPilot\\prc-tools /prc-tools
$ mount C:\\Program\ Files\\GNU\ PalmPilot\\sdk /PalmDev
The above bash commands will manually configure these mount points.
I want to use the Palm 4.0 (or later) sdk to build my program.
You specify the sdk you wish to use by using one of the following command
line arguments to the m68k-palmos-gcc compiler:
-palmos1 --> looks in sdk-1/
-palmos2 --> looks in sdk-2/
-palmos3 --> looks in sdk-3/
-palmos3.0 --> looks in sdk-3/
-palmos3.1 --> looks in sdk-3.1/
-palmos3.5 --> looks in sdk-3.5/
These relationships are defined in a specification file inside the prc-tools
installation directory:
C:\Progra~1\GNUPal~\prc-tools\H-i586~1\lib\gcc-lib\m68k-palmos\2.95.2-kgpd\specs
On line 88, there is a specification for the tag "*palm_sdk:". To add
a new sdk base, you simply add the flag you want and the directory to look
into, for example:
...%{palmos4:-4}
This command will add a new flag (-palmos4) and will look for
the headers in the "sdk-4" directory.
DISCLAIMER:
You should create a backup of your spec file before proceeding. Palm
Computing will not provide support assistance if you destroy your
specification files and cannot guarentee a clean upgrade path in the
future if you do so. You make these modifications at your own risk.
When using "make", wildcards are not available!
Ensure that the MAKE_MODE environment variable is set, and
contains the value "UNIX".
You can check if it is set by typing the following command
in the bash prompt:
$ echo $MAKE_MODE
UNIX
You should check your installation
(Win 95/98/Me or
Win NT/2k)
for your environment variables.
END OF FAQ
