I've found that I prefer ZGCC -- mainly because the installation is less intrusive and easier to clean up should you decide you want to remove it later. If you'd rather go the dev-img route, perhaps someone else can offer guidance on that.Prerequisites:
The first thing you should do is get the latest ZGCC from this site
. You'll need both the binaries image and the include files image. If you got ZGCC from some other site, it may not be the latest version and the instructions below may not work.
You're also going to need an SD card to put this stuff on (cramfs images cause all kinds of problems if you mount them from CF and then suspend your Z). You'll need enough free space for both images (minumum 9MB). The card does not have to be ext2/ext3 formatted -- FAT16/FAT32 will work just fine.
You have an SL-5600 so you shouldn't have to worry too much about your ROM version (unless you're using OZ ... then you'll have to find an OZ person to advise you).
You will have to do a bunch of command line stuff, so you need to have a terminal program (such as EmbeddedKonsole) installed.Instructions:
Put both images in the root of your SD card and then follow these instructions carefully
. You'll most likely want to use the steps described under Option 1
then do the steps under Configuring the Compiler
. The process is not
simple, but the instructions are very good and if you follow them exactly, everything will work fine. If you have problems, post the details of the step that's tripping you up and the results you're getting, and I'll try to offer suggestions.Caveats:
Note that there are no fancy IDEs to hold your hand when you're developing C/C++ on the Zaurus. It's good old-fashioned command line development. I don't know how they teach programming courses these days, but the majority of inexperienced programmers I meet seem to be completely lost without a GUI. You're going to have to write your source code in a text editor, save it, then go to a command shell and use a command like "gcc -o foo -lm foo.c" to build your program. If it doesn't work, you'll have to debug the hard way by sprinkling your code with debug printf statements or the slightly-less-hard way by using the GNU debugger (GDB). Don't get me wrong, all this stuff is perfectly usable and I actually prefer developing with command line tools, but it could be tough for a beginner (just learning C++ well
is enough to tax most mortal humans