Cacko doesn't use qtopia-1.7, it uses the qtopia that Sharp used to make the Z (1.5.4)
I've dug through ftp.trolltech.com and can't find the source to 1.5.4. wouldn't an upgrade to qtopia-1.7 be a useful step up from 1.5?
cacko has qt-embedded-2.3.2 libraries. I'm going to see if I can build qt-e-2.3.10 for arm and see what happens if I put the library onto my Z!
please bear in mind I'm a total noob to all this! Basically I've been building everything I can on x86 to see how it all hangs together. I've even played with building kernel 2.6.12 (x86) with experimental virtual frame buffer and had fun corrupting all my virtual console displays! At this moment, my X display is OK, but my console (ALT-F1 etc) is a mess of lines.
According to what I've read qtopia 2.1 apps are backwards compatible with qtopia 1.5 and if built using gcc 2.95 then should run on the standard Sharp rom (and hence Cacko).
Maybe some kinda hybrid rom would be possible as an intermediate stage
[div align=\"right\"][a href=\"index.php?act=findpost&pid=85538\"][{POST_SNAPBACK}][/a][/div]
they do promise that the communications between qtopia app and the display are backwards compatible, so I can't see why as long as the old versions of the libs are there that things should continue to work.
Qt/E 3.x is too big for PDA - even TT does not use it in Qtopia..
but is it slimmer than X? Would a good qt/X hybrid give good performance without the weight of debian/pdaXrom etc?
thanks very much for the replies, appreciated. I'm hoping Anton Mas'ky will pop up and enlighten me!
Paul