You will need the following things to use ePalm:
You will need the following things to use ePalm:
- A SmartEiffel Distribution
- This version of ePalm requires the
SmartEiffel 1.1 distribution from the smarteiffel website,
http://SmartEiffel.loria.fr
- PRC-tools
- the prc-tools collection of tools contains documentation,
header files, and an m68k crossover compiler. This version of
ePalm used the prebuilt debian packages prc-tools, prc-tools-doc,
prc-tools-m68k, and prc-tools-utils, version
2.2.90.cvs20030306-4. Others versions of prc-tools should work as
well.
- Ruby
- the scripting language Ruby is used for many ePalm script
tools, to generate source code, to script the compilation process,
etc. This version of ePalm used the premade Debian ruby package,
version 1.6.8-3; other versions may work as well.
- make/automake/autoconf
- The distribution of ePalm uses autoconf and
automake in conjuntion with the
make
utility to generate sample
programs, but you may use any make tool for your own code.
- pose
- The PalmOS Emulator is available from the Palm.com website,
but this version of ePalm used the premade Debian package pose,
version 3.5-1. Pose is used to emulate a palm device on your
desktop; you can also upload the generated packages to your
personal device should you wish (but this makes debugging tricky).
- ROM images
- Pose is an excellent emulator, but it will require ROM
images in order to function. Those cannot be distributed without
license, but are available from the Palm.com website for
registered developers who accept licensing agreements.
- A graphical debugger if you choose
- there is often no need for
a debugger if you design and implement your applications slowly
and carefully, but if you must debug, a graphical debugger that
interfaces with gdb is a big help; I used ddd, version 1:3.3.7-1.
I have not tested ePalm on any platform other than Linux for
development and PalmOS 4.0, and in any case its performance on ANY
platform is not guaranteed.