I get the feeling that the rootless option although pretty powerful, gets toocomplicated as soon as you want to run several X clients simultaneously,i.e. multiple DISPLAY's, from what I read in the rootless post. I get theimpression it is being abandoned.

QUOTE(bam @ Jun 16 2006, 12:51 AM)

I was hoping for a qtopia version...

I'm very hesitant to spend time learning about the Qt API to provide a Qt-basedLINUX conversion of Space Trader. I feel an X11-based version would allowalmost anyone with running LINUX to enjoy the game ultimately. I am very interestedin this particular "packaging of an X/Qt environment", whether it be just the X server,apps and a gcc development environment, OR the full pdaXrom under X/Qt.

Since I wish to get this setup on a 5500 first (then an 6000), I am more interestedin saving resources and living without the full pdaXrom.

I get the feeling that the rootless option although pretty powerful, gets toocomplicated as soon as you want to run several X clients simultaneously,i.e. multiple DISPLAY's, from what I read in the rootless post. I get theimpression it is being abandoned.

QUOTE(bam @ Jun 16 2006, 12:51 AM)

I was hoping for a qtopia version...

I'm very hesitant to spend time learning about the Qt API to provide a Qt-basedLINUX conversion of Space Trader. I feel an X11-based version would allowalmost anyone with running LINUX to enjoy the game ultimately. I am very interestedin this particular "packaging of an X/Qt environment", whether it be just the X server,apps and a gcc development environment, OR the full pdaXrom under X/Qt.

Since I wish to get this setup on a 5500 first (then an 6000), I am more interestedin saving resources and living without the full pdaXrom.

actually, the rootless mode thing is not as powerful as hoped for imho, but I got around the DISPLAY issue, etc..., ie you can have multiple rootless apps running concurrently, but I wouldn't recommend it because the Z doesn't have that much memory. For example, and these are just numbers I use for illustration purpose and not the real memory usage of Xqt, but lets say the whole X environment uses 50MB of memory plus apps, the rootless env would perhaps use 35MB, but if you run two rootless apps, then it would be 2 x 35MB + app1 + app2, whereas the full X environment would just be 50MB + app1 + app2it doesn't really matter what you do, memory usage is the big problem and the 64MB of RAM in the Z is really the bottleneck. a swapfile is very helpful, but it suffers from the slow disk i/o

anyway, I am trying to get Qt 3.3.5 working under XQt, not so much joy so far...

[...] a swapfile is very helpful, but it suffers from the slow disk i/o

Disk? What disk? I have no disk! I use a swapfile on SD myself!

Sorry to hear Qt 3.3.5 is frustrating you. I look forward to trying any newrelease you provide, and hopefully it will work on the SL-5500.

Best of luck! John

when I say disk its a general term for microdrive, SD/CF cards, usb stick....

Qt3 is still giving me grief. i compile it every night with different options and every morning I find it compiled successfully without errors, but it won't run or link apps I think I am getting closer though, getting different linker errors so seems like I am on the right track. A few more overnight compilations and I might get there...Once qt3 is compiled, I will try to compile kde3 and then I would have a full environment (except SDL which is still trouble).why am I doing this? I know kdemicrolibs exists and can be used to port qt3/kde3 apps for qte, but I want a full X environment with qt3 and kde3 running under X/Qt.Took me a day to compile Qt3 Designer natively on pdaXrom, but I want it on Sharp ROM too

Your work is truly amazing and beneficial to newbies like me. I am looking forward to try out your pdaxqtrom 0.8.0.

I have an older version of the gcc complier installed using the install script but I would like to uninstall it completely/cleaning so I can install the upcoming gcc release (with QT3). What would be the best way to delete it? I am not sure how to remove all those symbolic links created during installation.

Your work is truly amazing and beneficial to newbies like me. I am looking forward to try out your pdaxqtrom 0.8.0.

I have an older version of the gcc complier installed using the install script but I would like to uninstall it completely/cleaning so I can install the upcoming gcc release (with QT3). What would be the best way to delete it? I am not sure how to remove all those symbolic links created during installation.

Thanks.

the links haven't changedupdating the zgcc image is quite simple. just replace the cramfs or squashfs file (after you unmount the image first of course)then run zgcc-setup just to be sure

anyway, I finally managed to compile qt3 in such a way that I can now successfully compile the samples and tutorials.... now I have to rebuild everything with shared libraries instead of static linking...

look, qt3 sample app under x/qt it's getting there but still quite a lot of problems to iron out...

Your work is truly amazing and beneficial to newbies like me. I am looking forward to try out your pdaxqtrom 0.8.0.

I have an older version of the gcc complier installed using the install script but I would like to uninstall it completely/cleaning so I can install the upcoming gcc release (with QT3). What would be the best way to delete it? I am not sure how to remove all those symbolic links created during installation.

Thanks.

the links haven't changedupdating the zgcc image is quite simple. just replace the cramfs or squashfs file (after you unmount the image first of course)then run zgcc-setup just to be sure

anyway, I finally managed to compile qt3 in such a way that I can now successfully compile the samples and tutorials.... now I have to rebuild everything with shared libraries instead of static linking...

look, qt3 sample app under x/qt it's getting there but still quite a lot of problems to iron out...

still no joy with qt3. the sample apps compile and link fine when doing it statically but that results in huge binaries... but linking them with shared libraries don't work still so i decided to compile binutils 2.16 and see if that's any better.... might as well compile automake and autoconf as well while I'm at it...

Your work is truly amazing and beneficial to newbies like me. I am looking forward to try out your pdaxqtrom 0.8.0.

I have an older version of the gcc complier installed using the install script but I would like to uninstall it completely/cleaning so I can install the upcoming gcc release (with QT3). What would be the best way to delete it? I am not sure how to remove all those symbolic links created during installation.

Thanks.

the links haven't changedupdating the zgcc image is quite simple. just replace the cramfs or squashfs file (after you unmount the image first of course)then run zgcc-setup just to be sure

anyway, I finally managed to compile qt3 in such a way that I can now successfully compile the samples and tutorials.... now I have to rebuild everything with shared libraries instead of static linking...

look, qt3 sample app under x/qt it's getting there but still quite a lot of problems to iron out...

still no joy with qt3. the sample apps compile and link fine when doing it statically but that results in huge binaries... but linking them with shared libraries don't work still so i decided to compile binutils 2.16 and see if that's any better.... might as well compile automake and autoconf as well while I'm at it...

well, got it finally! updated the complete zgcc image (gcc compiler 2.95.3 and all the bundled tools: autoconf 2.59, automake 1.9.2, coreutils 5.0, diffutils 2.8.1, gawk 3.1.5, grep 2.5, sed 4.0.9, texinfo 4.8 and binutils 2.16) and was able to compile glibc 2.2.2 and fixed fesetenv and fegetenv.with this updated compiler and tools as well as a bundled fixed glibc, I managed to compile qt 3.3.6 natively. currently, qt apps compile fine, except the font is messed up new zgcc image will be uploaded soon. i am gonna fix the font problem later. this new image is going to be quite big since it includes quite a lot more files but it can compile so much more stuff.

yep, it's always been there, since when I first tried to compile a X11 app with it...if you install zgcc and the pdaXqtrom-base images, then you have everything you need, headers, config and libraries, otherwise, you will need to install the ipk for the libs which are all available from http://www.thegrinder.ws/Meanies_XQT/pdaxqtrom/feed/base/

zgcc 2.95.3 is the most up to date dev image with lots more updated tools, patched header files and additional static libraries for static linking. a patched glibc-2.2.2. is also included. this image is able to compile almost anything that does not require gcc 3.x

I tried to install the pdaxqtrom base, app, java, dictionary, and zgcc images all together with the provided shell script to my c1000 (loaded with cacko rom). But I always get the following errors during installation: