I just complied the qt3 version on my Z in minutes. It is pretty minimal, as is--some tweaking and customizing would need to be done before it is really a good alternative.
I bring it up because it runs on x11, doesn't seem to take much time to load libs to run dillo. it also seemt to be quicker at loading qt apps (since qt is already loaded). ta qlwm project page shows konqueror running on it. possibly this could be the basis of a nice x11 gui for the Z running light kde stuff?

I guess the next step is to see how 'full' a konqueror can be made for it?

This sounds interesting adf, I did like messing with kde on my Z but although it was fun I like to get stuff done as well!

Diesel1.

This sounds interesting, do keep us updated on your progress since it seems like a promising alternative. Any idea what the memory/etc footprint is like compared to say an IceWM setup?

If you, like me, are looking for the perfect lightweight WM, look at EvilWM. It compiles extremely quickly, and uses only about 1MB of RAM. You don't get fancy borders or a taskbar, but it works well. Note that if you want to edit the source to change the keys/add a few more, it is not hard to do at all and a non-programmer could do it.

flippping between the two shows qlwm with about 11 megs free and iceewm with about 2 megs free. I don't think it is very meaningful, though as icwm/rox are doing much more and I really haven't establisshed any controls.

what I'm hoping to see in qlwm is something like fvwm or ede, but with less qtlib lag, given that qtlibs will be loaded to run the gui. thi woyld make a beefy konq (-e ) a more reasonable alternative to firefox in X11---something that might be of interest both due to eabi issues with FF in Angstrom, our apparent inability to gt FF2 built in pdax, the sheer size of the FF footprint/ and my guess that the iphone safari will spin off useful tidbits.

I posted a link to a qlwm site with sources on t eh konq embedded thread, if anyone cares to tinker. while it is fast enough, it needs a lot of Z specififc twaking

Hi all.
Did anyone try to compile it with Qt4? the BIG advantage is that this version consumes less memory and its design is more "granular" (so it should boot quicker). I've seen reduction in memory usage up to a 50% (in projects not related at all to the Zaurus.).

On my side, I am still unable to compile Qt4, I'll keep trying

Cheers

Qt4 would be a big gain--good luck

As I remeber Qt4 needs at least glibc 2.3.2 (pdaXrom have 2.2.5 by default). Then it is recommended (but not necessary) to use gcc 4.x (can be easiliy compiled). Configure of qt4 by default can't understand that armv5te is arm and uses arch=generic. It may result in compiller error when it tries to compile x86 asm on arm... In theory Qt4 can be build (Angstrom have packages with Qt 4.3.0), but on pdaX it is very painful becouse of outdated libs.
P.S. Since Qt4.3.0-rc1 qt have experimental support of iwmmxt instructions, but as google says it fails to build with that options. You can try configure -iwmmxt

Thanks for the hints!

After trying the cross compiling for a while I simply gave up, Qt is trying to build some tools to use them afterwards in its own build process... so I had to go native (at zaurus speeds)

I knew the bit about the compiler, I had to disable the precompiled headers for having something going (it complained about some pch error after 3 hours of native compiling).

And yes, maybe the problems I am having are related to glibc (actually this brings light to the spot!) Does anyone know if there is an updated glibc version for pdaXrom?

Thanks all.
E

No Problem. I was googling about Qt4 errors for a few days, after that I've realized that it is faster to kill pdaXrom and use Gentoo. Now it is compiling (30h already) without any warning...


Yeah, Qt is very big library. It should took around 50h to compile it natively.


In fact there is one thing that you haven't found - it says something like:
Warning: bla-bla-bla will always fail!
this is the most dangeourus thing - it is becouse of glibc (was fixed in 2.3.2 only), and that's why Qt4, even if you manage to build it won't work (in fact it shouldn't build at all - after ~8h you'll get a lot of asm-related errors becouse of that little warning).


There was 2.3.2 for pdaXrom 1.1.0 Beta1 somewhere. But be careful - glibc 2.2.x and 2.3.x can be binary incompatible

P.S. You probably will need http://svn.debian.org/wsvn/pkg-kde/branche...file&rev=0&sc=0 and http://svn.debian.org/wsvn/pkg-kde/branche...file&rev=0&sc=0

Where is this Gentoo for Zaurus? Is it easy to set up/boot? I may be interested...

I think the guys who were doing gentoo moved to debian--maybe look at the debian uboot thread?

Generic stage for pxa27x based pda's It have wrong kb layout, you need to unpack it to cf/sd card and manualy fix fstab and /etc/conf.d/net (to use usb-net) then you can emerge other parts of system.
Root password is gent00
http://gentoo-wiki.com/HARDWARE_PDA - here is howto.

Standart stage for pxa25x and other pda's that doesn't support iwmmxt.
Stages are rather fresh (iwmmt stage was built around 2 month ago, and xscale stage was built 10 day ago)

Here are a lot of interesting things there like portage-overlay with some pda-specific things (evtouch driver for pda's, patched xorg-kdrive with tslib support, precompiled binary packages, etc.)
Here are some additional links:
http://forums.gentoo.org/viewtopic-t-518041-start-75.html
http://forums.gentoo.org/viewtopic-t-8090-start-25.html