|This page is hopelessly outdated. Please do not use it!|
gcc), loader, (
ld), debugger (
gdb), etc., that support cross-compiling to Motorola 68K machine code, which is what the Pilot runs.
gdb-4.16in the same level.
Makefileand make the following changes:
HOSTvariable to the correct type for your machine. Or better yet, apply this patch, which deletes all references to the HOST variable, and lets
configurefigure out by itself what machine you are running on.
PREFIXvariable to where you want to install things. Under this directory,
lib, etc. will be created. I would recommend using a place for Pilot-specific stuff, such as
CFLAGSto suit your taste or needs.
make patchThis will apply some patches to the gcc, gdb and binutils directories, that are needed to support Pilot.
make gnutoolsThis will compile and install the contents of the gcc, gdb and binutils directories. So you have to do this with the appropriate privileges for the files to be installed (it is not a good idea to compile things as root, but oh well...)
makeThis will build the stuff in prc-tools, and leave you with a bunch of tools for manipulating resources, building
make installThis will install everything where you specified.
READMEfile in prc-tools. It contains these same instructions, plus some additional information that you may find useful.
libXpminstalled, go and get it. I will not cover that process here.
xcopilot-v0.4, and apply the patch.
mx/Makefile, and do the following changes (not all are applicable to all files):
LIBDIRto where you want to put things. In
LIBDIR, only the icons for the program are put.
CCto whatever you find appropriate, but I wouldn't recommend changing it from gcc.
LFLAGSto adequate values so that the compiler and loader find the appropriate include files and libraries.
make xcopilotAnd the magic should be done. Now do
make installAnd the binary and icon files will be put where you indicated.
pi-getromprogram from pilot-link. The syntax is:
pi-getrom <port>It should crank away for a while, and you end up with a file called
pilot.rom.x.y, where x.y is the ROM version of your Pilot.
~/.xcopilot/, and set the
XCOPILOTDIRenvironment variable to point to that place. In the same directory, create
pilot.romas a link to the file you just created.
xcopilotand you should get a running Pilot on your screen.
pi-getramfor fetching a copy of your Pilot's RAM. Then you can have an identical copy of your Pilot in your desktop!
Diego Zamboni Last modified: Mon Jun 22 11:24:17 EST 1998