Messages

1

Qt/Qtopia / 3d Programming

« on: December 02, 2004, 10:18:30 pm »

Uhm, so Zsurface can't run in VGA. tks erio.

Regarding do SDL:
So let's see, if I do actually want to do some 3D programming on the zaurus...say a 3D First Person Shooter, is it possible to do it plainly just on SDL without any softGL lib like klimt?

Yeah, sorry about that. I have a patched version of the Klimt CVS tree that enables a #define to enable the use of a regular memcpy to a char** for the blitting of the display that should be more portable than the Zsurface library.

As has been noted you can always use the SDL backend. Another option is to use the klimt extensions to manually pass the backbuffer memory pointer, although then you have to handle the screen bliting manually through your own memcpy or whatnot. If any one is interested I can upload it for others to try. Yet another option is for me to get some motivation and patch Zsurface to handle full VGA displays.

Ryan

2

Qt/Qtopia / 3d Programming

« on: July 19, 2004, 03:57:37 pm »

 
Ryan,

does that mean that I don't need freeglut for building apps using klimt? If so (I can't believe) what's the difference and why do I (might) need freeglut?

Georg

Georg,

That is correct, freeglut is not required for building apps directly using Klimt, anymore than you need to use freeglut on your PC to build OpenGL apps. It just provides a windowing toolkit with event handling and some additional utility functions. From the freeglut homepage  "GLUT (and hence freeglut) allows the user to create and manage windows containing OpenGL contexts on a wide range of platforms and also read the mouse, keyboard and joystick functions."

If you look at the examples provided in the source archive, you'll find examples of both types of applications. simple_linux_qte and KlimtDemo_qws, in the klimt/test directory, just use libKlimt and the regular Qt api. The test appliction in the freeglut/test directory uses the GLUT api to perform a similar task.

Ryan

3

Qt/Qtopia / 3d Programming

« on: July 19, 2004, 12:46:04 pm »

Ryan,

finally I made it (somehow) to build a freeglut.so. Could you please be so kind and
explain the dependencies and meanings of the several libs contained in your source-package to me? What are the minimum requirements to use klimt on the
Z5500? I can't await to start with that stuff ... g*

Thanks a lot,
Georg

Georg,

Klimt just requires libqpe and libqte. Nothing else is required.
Freeglut requires libqpe, libqte, libKlimt, libqpc, libqtc and libglut2qevent. libqpc and libqtc are C bindings to libqpe and libqte respectively, and libglut2qevent handles the mapping of the glut main loop into a qevent loop. The source code to all 3 of those libraries is also in the source tarball.

To run apps I generally use LD_PRELOAD, ie.

LD_PRELOAD=./libKlimt.so ./SomeKlimtApplication

or

LD_PRELOAD=./libKlimt.so:./libglut2qevent.so:./libqtc.so:./libqpc.so:./libfreeglut.so ./SomeGLUTApplication

Alternatively you could place the libraries somewhere in your LD_LIBRARY_PATH

Good luck,

Ryan

4

Qt/Qtopia / 3d Programming

« on: July 19, 2004, 01:17:16 am »

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.

Ryan

5

Qt/Qtopia / 3d Programming

« on: July 18, 2004, 12:14:23 am »

Georg,

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

6

Qt/Qtopia / 3d Programming

« on: July 16, 2004, 12:49:24 pm »

 
Hi,

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

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

7

Qt/Qtopia / 3d Programming

« on: July 07, 2004, 11:25:08 pm »

Andreas,

Source archive

Ryan

8

Qt/Qtopia / 3d Programming

« on: July 07, 2004, 04:11:30 am »

Flex,

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.

Ryan

9

Qt/Qtopia / 3d Programming

« on: June 24, 2004, 03:07:56 am »

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.

Cheers,

Ryan

10

Software / Hotmail & Mail App

« on: May 31, 2004, 06:21:00 pm »

You could always try cross-compiling hotwayd for the ARM, and running that, then all you would need is a POP3 mail client on the Z.

11

Zaurus - pdaXrom / Cross compiling issues

« on: March 16, 2004, 02:16:59 pm »

Check to make sure you are performing dynamic linking.

12

General Discussion / USB Storage ported to 5xxx ROM\'s ?

« on: February 27, 2004, 09:02:45 pm »

Code: [Select]

+++ sa1100.c    2004-02-27 19:19:34.628738128 -0500

@@ -440,6 +440,7 @@

                                         udc_interrupts, *(UDCSR), *(UDCCS0), *(UDCAR));



                        usbd_device_event (udc_device, DEVICE_RESET, 0);

+                       usbd_device_event (udc_device, DEVICE_ADDRESS_ASSIGNED,0);

                }



                if (status & UDCSR_SUSIR) {

To compile i used the 860 kernel source with the drivers/usb/device/bi directory from the 5500 kernel source. I then patched the sa1100.c driver as above (1 line)  copied the sl5500 config (arch/arm/def-configs/collie) to .config. I then manually copied the CONFIG_USBD_STORAGE section from the boxer config into the .config.

After that it was a simple matter of building the kernel and modules and copying the files over to the Z and using modified versions of lardman\'s scripts to load the appropiate modules.

Cheers and good luck

Ryan