Palm Computer - installing my development environment

my palm development What do I have on mine? wish or idea list Why I love my Palm & Palm vs Pocket PCs old & maybe out-of-date links messing with graffiti

• Install Cygwin
• Read cygwin instructions: installing prc-tools on cygwin
• Install cygwin specifying server that holds prc-tools package for cygwin (this will also make sure essential tools like make are installed)
• Get an sdk www.palmos.com/dev/tools/
• Pull sdk together with prc tools (put in /PalmDev, tell prc-tools where sdk is) RTFM.
• Don't forget to get pilrc pilrc (palm resource compiler (maybe this now comes when you select prc-tools in cygwin install)

Makefile-cygwin-readme I'm making these notes as prc-tools didn't quite install exactly as the installation notes said. It could well be to do with the confused collections of cygwin versions on my PC.

If you're interested in doing palm development with cygwin you probably already have cygwin. What? You've already got linux! Oh well then you're set. You can get the same prc-tools development environment going with much less hassle. :) Anyway back to people stuck with windows. At least you are familiar with unix a little, yes? If not it is well worth installing cygwin anyway. It's a great way of learning unix tools. It may take you a few years! :) Cygwin FAQ

When installing cygwin make sure and install development tools. (You can go back and check more boxes to install more stuff. make is essential I would always have others (perl, gcc (for Cygwin), sed, awk, grep, ...)

after Cygwin is working you get the palmOS development tools. Tools & links to other tools from Palm here: Read cygwin instructions: installing prc-tools on cygwin

• 1. Get an SDK, e.g. sdk4.0, look here: www.palmos.com/dev/tools/ For cygwin, install sdk in a PalmDev directory somewhere. This is mounted as /PalmDev for cygwin e.g. install sdk in D:\Palm\PalmDev\sdk mount -tf "D:\Palm\PalmDev" /PalmDev
  I also keep working development directories in /PalmDev. And directories for palm tools.

  e.g.
  [bash] ...src/: ls /PalmDev/sdk
  Palm OS 4.0 SDK ReadMe.txt  Readme Before Deleting.txt  lib/
  Palm OS SDK Licenses/       include/
  
  [bash] ...src/: ls /PalmDev/sdk/include/
  BuildDefaults.h  Dynamic/             PalmOS.h        PalmTypes.h  Pilot.h~
  BuildDefines.h   Extensions/          PalmOS.pch      PalmUtils.h  header.gcc
  Core/            PalmCompatibility.h  PalmOS.win.pch  Pilot.h      libraries/
  
  (that Pilot.h is a hack for converting old types (from sdks before 3.5) lazily)
  e.g. see paper about upgrading
  

• 2. Get prc-tools prc-tools.sourceforge.net and install. This is getting easier! Now you just run Cygwin installer (Setup.exe) and point it to the server where there is a prc-tool package for cygwin available.

  Your mileage may vary ... but ... when I installed them I had to do a few extras to get full use from them. And partially because I wanted some software to compile without me messing with it's source code. Many palm programs should work with none or just some of the following adjustments: They installed here:

  ls /usr/m68k-palmos/        
  include/  lib/  real-bin/
  

  And in /usr/bin:

  ls /usr/bin/m68k-palmos-*
  /usr/bin/m68k-palmos-addr2line.exe*  /usr/bin/m68k-palmos-obj-res.exe*
  /usr/bin/m68k-palmos-ar.exe*         /usr/bin/m68k-palmos-objcopy.exe*
  /usr/bin/m68k-palmos-as.exe*         /usr/bin/m68k-palmos-objdump.exe*
  /usr/bin/m68k-palmos-c++.exe*        /usr/bin/m68k-palmos-protoize.exe*
  /usr/bin/m68k-palmos-c++filt.exe*    /usr/bin/m68k-palmos-ranlib.exe*
  /usr/bin/m68k-palmos-gasp.exe*       /usr/bin/m68k-palmos-size.exe*
  /usr/bin/m68k-palmos-gcc@            /usr/bin/m68k-palmos-strings.exe*
  /usr/bin/m68k-palmos-gdb.exe*        /usr/bin/m68k-palmos-strip.exe*
  /usr/bin/m68k-palmos-ld.exe*         /usr/bin/m68k-palmos-stubgen.exe*
  /usr/bin/m68k-palmos-multigen.exe*   /usr/bin/m68k-palmos-unprotoize.exe*
  /usr/bin/m68k-palmos-nm.exe*
  

  Those files marked witn @'s are links which I made. Different versions of cygwin may have things in different places (but actually this is my fault for having old versions of cygwin lying around).
• 2.1 Sometimes you want something like this: e.g. When your makefiles set CC=m68k-palmos-gcc

  ln -s  /usr/m68k-palmos/real-bin/gcc /usr/bin/m68k-palmos-gcc
  

• 2.2 Sometimes you want something like this:

  mkdir /usr/m68k-palmos/bin
  cd /usr/m68k-palmos/bin
  ln -s /usr/bin/m68k-palmos-addr2line.exe addr2line.exe
  ln -s /usr/bin/m68k-palmos-ar.exe ar.exe
  ln -s /usr/bin/m68k-palmos-as.exe as.exe
  ln -s /usr/bin/m68k-palmos-c++.exe c++.exe
  ln -s /usr/bin/m68k-palmos-c++filt.exe c++filt.exe
  ln -s /usr/bin/m68k-palmos-gasp.exe gasp.exe
  ln -s /usr/bin/m68k-palmos-gdb.exe gdb.exe
  ln -s /usr/bin/m68k-palmos-ld.exe ld.exe
  ln -s /usr/bin/m68k-palmos-multigen.exe multigen.exe
  ln -s /usr/bin/m68k-palmos-nm.exe nm.exe
  ln -s /usr/bin/m68k-palmos-obj-res.exe obj-res.exe
  ln -s /usr/bin/m68k-palmos-objcopy.exe objcopy.exe
  ln -s /usr/bin/m68k-palmos-objdump.exe objdump.exe
  ln -s /usr/bin/m68k-palmos-protoize.exe protoize.exe
  ln -s /usr/bin/m68k-palmos-ranlib.exe ranlib.exe
  ln -s /usr/bin/m68k-palmos-size.exe size.exe
  ln -s /usr/bin/m68k-palmos-strings.exe strings.exe
  ln -s /usr/bin/m68k-palmos-strip.exe strip.exe
  ln -s /usr/bin/m68k-palmos-stubgen.exe stubgen.exe
  ln -s /usr/bin/m68k-palmos-unprotoize.exe unprotoize.exe
  

  So before calling make you can set PATH=/usr/bin/m68k-palmos-gcc:$PATH Then gcc or nm or objdump or whatever will call the palm version, not the cygwin version.

  This is the useful line that made the above easy: [bash] ...src/: ls /usr/bin/m68k-palmos-* |sed s/\*//|sed "s#\(.*palmos-\)\(.*\)#ln -s \1\2 \2#"

• 2.3 Sometimes when porting tools you get problems with undefined types or missing include files. The following helped me:

  cd /usr/m68k-palmos/include/
  ln -s /usr/include/stdlib.h unix_stdlib.h
  ln -s /usr/include/string.h unix_string.h
  
  ls /usr/m68k-palmos/include/
  ctype.h   mathf.h   stdlib.h  unix_stdlib.h@
  errno.h   setjmp.h  string.h
  malloc.h  stdio.h   sys/      unix_string.h@
  

• 3. If you want to compile pilot resource files (for dialog boxes, frames etc....) Get pilrc pilrc (palm resource compiler Forget about the gui for cygwin for the moment (port from X to cygwin needed). You can easily compile pilrc itself though by hand:

  gcc -O2 -g -DUNIX -DWINGUI pilrc.o lex.o util.o bitmap.o main.o -o pilrc

  You can get quite a few GUI resource editors precompiled if you want. You might want to put the following in win.c:

  #ifndef UNIX
    /* cygwin */
    #include "afxres.h"
  #endif
  
  AND:
  #ifdef UNIX
    /* cygwin /usr/include/w32api/winbase.h */
    int APIENTRY WinMain(HINSTANCE hinst, HINSTANCE hinstPrev, LPSTR lpszCmdLine, int nCmdShow)
  #else
    int PASCAL WinMain(HANDLE hinst, HANDLE hinstPrev, LPSTR lpszCmdLine, int nCmdShow)
  #endif