Porting TinyGL would be pretty easy - but performance would be very poor, due to the use of floating point for calculations (no FP hardware on the Zaurus). What's needed is a fixed point implementation of a rendering engine. I kind of started one based on the 2D fixed-point rendering engine I wrote for the Dreamcast Flash player, but I never really made any progress on it (lack of time really). It's obviously possible (just try the demo of Interstellar Flames to see what can be achieved), but it's down to who's got the time to do it?

You could use Klimt, a GPL'd fixed point 3D library that whose API is virtually identical to the OpenGL/ES (OpenGL for Embedded) spec. CVS doesnt compile at the moment for Linux/QTE but the last release version did, as I haven't sent a recent patch back upstream to the maintainer in a while.

If you are interested I could post my Freeglut port and the related libraries necessary for programming for the Zaurus using the GLUT api. It requires a patched Klimt CVS lib, a back port of the KDE projects QT C bindings, and a custom event loop library that handles the translation between the QT event loop and GLUTs main loop. Altogether they are several MB compiled, and I dont have any webspace to host binary ipks or source tarballs, so they've been collecting virtual dust on my PC for a few months.

Note: I've only ever tested them on my 5500, any other Z may or may not work without a little manual source patching.

Since I am working on an OpenVRML port for the Zaurus (5500 too), I am highly interested in this topic. Ryan please upload your binary libs (and sources) to sourceforge (or somewere), I 've successfully compiled klimt but freeglut is still missing.

You need them packaged into .ipks? I generally just upload the .so's and applications to my Z and use LD_PRELOAD to run them. If so I will try to find the time to package them this week, as soon as I get the opportunity to upload them to SF.

it's quite interesting for me what you're discussing about. I'm thinking about implementing a terrain modeler for my (and others) Zaurus 5500 for visualization of DEMs. I'm running OZ3.3.5. I just tried to compile klimt for linux ... but I failed when building freeglut. Does anybody have a collection of all (working) required sources to build klimt for Linux and QPE? Thanks, Georg

it's quite interesting for me what you're discussing about. I'm thinking aboutimplementing a terrain modeler for my (and others) Zaurus 5500 for visualizationof DEMs. I'm running OZ3.3.5. I just tried to compile klimt for linux ... but I failed whenbuilding freeglut. Does anybody have a collection of all (working) required sources tobuild klimt for Linux and QPE?Thanks,Georg

Georg,

What errors do you get when trying to build it? The source archive I posted is a straight copy from my work directory, and it all builds fine for me in there. The only other requirements to build it would be a working development enviroment AFAIK.

it's quite interesting for me what you're discussing about. I'm thinking aboutimplementing a terrain modeler for my (and others) Zaurus 5500 for visualizationof DEMs. I'm running OZ3.3.5. I just tried to compile klimt for linux ... but I failed whenbuilding freeglut. Does anybody have a collection of all (working) required sources tobuild klimt for Linux and QPE?Thanks,Georg

Georg,

What errors do you get when trying to build it? The source archive I posted is a straight copy from my work directory, and it all builds fine for me in there. The only other requirements to build it would be a working development enviroment AFAIK.

Ryan

Ryan,

sorry, I'm new in the forum. I tried it using the sources from freeglut's website. Where can I find your sources? My development environment (KDevelop) works fine for my other qpe-projects ...

it's quite interesting for me what you're discussing about. I'm thinking aboutimplementing a terrain modeler for my (and others) Zaurus 5500 for visualizationof DEMs. I'm running OZ3.3.5. I just tried to compile klimt for linux ... but I failed whenbuilding freeglut. Does anybody have a collection of all (working) required sources tobuild klimt for Linux and QPE?Thanks,Georg

Georg,

What errors do you get when trying to build it? The source archive I posted is a straight copy from my work directory, and it all builds fine for me in there. The only other requirements to build it would be a working development enviroment AFAIK.

Ryan

Hi Ryan,

in the meanwhile I've found your sources but I still can't build the libs. Which KDevelop version do you use? I'm using 2.1.5 so that I can't use your project files. I tried to build freeglut_qws with qmake and the .pro file. Make fails with something like 'no rule defined to build /usr/lib/qt3/mkspecs/qmake.conf'. I don't intend to upgrade to KDevelop 3.0.x at the moment because then my Zaurus-Dev-Env. might not work anymore. Any suggestions?

I'm running a self compiled version of Kdevelop from CVS, but that shouldn't matter, as you can manually run qmake to build the makefiles assuming you have the correct qmake setup.

Extract the attached qws.tgz somewhere, and then either export the QMAKESPEC environment variable to ${PATH_WHERE_YOU_EXTRACTED_IT}/qws/linux-sharp-g++ or specify that on the qmake command line with the -spec argument. You'll have to set your QTDIR variable to your qt/embedded directory first to ensure you dont pull in any native qt3 directories.

I'm running a self compiled version of Kdevelop from CVS, but that shouldn't matter, as you can manually run qmake to build the makefiles assuming you have the correct qmake setup.

Extract the attached qws.tgz somewhere, and then either export the QMAKESPEC environment variable to ${PATH_WHERE_YOU_EXTRACTED_IT}/qws/linux-sharp-g++ or specify that on the qmake command line with the -spec argument. You'll have to set your QTDIR variable to your qt/embedded directory first to ensure you dont pull in any native qt3 directories.

Ryan

Ryan,

thank you. Now I can compile but then the linker fails with 'cannot find lXext' although XFree86-devel is installed and the libs (libXext.a and libXext.so) are in the X11-libs-dir.

thank you. Now I can compile but then the linker fails with 'cannot find lXext' although XFree86-devel is installed and the libs (libXext.a and libXext.so) are in the X11-libs-dir.

Georg,

Looks like its still pulling native libraries in... linking againt Qt/Embedded does not require any X libraries to be present at all... and in fact linking against them is generally a sure fire way to have your app fail when you try to run it on the Z.