Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - zaazoo

Pages: [1]
1
Zaurus - pdaXrom / X11 Headers?
« on: March 23, 2005, 06:43:18 am »
They are shipped with the cross-compiling sdk, here is a sample configure for rat

#!/bin/sh
CC=armv5tel-linux-gcc ./configure --prefix=/net/tester/zaurus \
        --build=i686-pc-linux-gnu --host=arm-pc-linux-gnuoldld \
        --x-includes=/opt/arm/3.3.2-vfp/armv5tel-cacko-linux/X11R6/include \
        --x-libraries=/opt/arm/3.3.2-vfp/armv5tel-cacko-linux/X11R6/lib \
        --with-tcltk-version=8.4 \
        --with-tcl=/opt/arm/tcltk-8.4 \
        --with-tk=/opt/arm/tcltk-8.4 \
        --enable-ipv6 \
        "$@"

I could not locate them in the native sdk though  

hope this helps

2
Zaurus - pdaXrom / Did Anyone Get To Use Glut Lib From Mesa3d ?
« on: March 17, 2005, 04:24:37 am »
Hi all

I am porting an appllication running on top of glut/GL stuff
I was glad to figure that the mesa3d ipkg provided for this library
however at the very first call to glutInit, i get a fatal error message stating that
GLUT: Fatal Error in v-eye: visual with necessary capabilities not found.  

Having some experience from previous ports, I know that this rather unexplicit message can happen with displays not running with 24-depth, and since it is the case as per xdpyinfo, I fancy this is my problem.  

So I tried to dig a bit in the X server config, and came out with only one way to run in 24-bits, namely by changing /usr/X11R6/bin/startx and adding X option
-screen 640x480x24

however even this does not work, and in fact the results of xdpyinfo does not change at all, even if I try other -screen options.

So my questions are
- does anyone know how to get the kdrive server to run with 24-bits (if feasible at all)
- did anyone get to successfully run an app. under libglut, knowing that glutInit is the very first call to this library and that none of the command-line args it may recognise seem to have any chance to improve the situation. If yes, did this need an X server reconfig ?

Thanks in advance

3
Zaurus - pdaXrom / Status Update..
« on: December 17, 2004, 11:39:41 am »
Hi there

I'm going back to the initial purpose of this thread - Sorry if I catch up a bit late on this.
fyi, I am not using the unit as a pda for my daily work, so I am probably not typical. I dont care much about the UI as such, but others did extensively address this before.

I've been building some packages such as tcl/tk (the devel ipkg was nowhere to be found), tcpdump, and was planning to make rsync and cvs. I am also interested in audio/video tools such as vic and rat, videolan. Of interest to me is also linux-wlan-ng and I found in another thread that someone had ipkg'ed that already.

I tried both the cross-compiler and native sdk's. At this stage I would need a few enhancements if I was to improve my building rate.

- gdb not working (i.e. not triggering breakpoints) is a major drawback. I figured this was a known bug and really hope this is fixed by now.

- cross-compiling is way faster but still has annoying bugs. Apart for the usual configure specials that cannot run in x mode, I found out the cc1 frontend to generate x86 asembler instructions occasionally (when building tcpdump I encountered that on quite a few source files). When this happens I have to switch to the native toolchain, and for that rsync will be much helpful.

Getting a more extensive ipkg feed would be a great improvement for pdaxrom. btw, I would volunteer to package some of these softwares - and get a devel account if needed - if the current issues could be fixed.

Pages: [1]