I've updated Developer Image:

- Added UIC (UI Compiler)
- Added tmake
- Added qembed - File and Image Embedder
- Added man, groff and a hole bunch of man pages
- Added VIM

Now having UIC and tmake in place, it's possible to build Qtopia GUI applications (not only console ones) on board your Zaurus!

Please, note that this version uses squashfs filesystem instead of cramfs, so you'll need a kernel module. See the this thead for details:

http://www.oesf.org/forums/inde...?showtopic=8323

The new Developer Image 1.6 can be downloaded here:

http://www.oesf.org/downl...dev-img-1.6.zip

Some recommendations: compiling C++ programs will each up most of your memory. It's highly recommended to create a swapfile of 32 Mb or more and disable some of the memory-coinsuming fast load applications, like KO/Pi PIM apps. Even then you may get Low Memory messages from Qtopia with large source files, so it's also recommended to split them into smaller ones.

Cool!! I've been using a modified zgcc but I never got around to putting tmake in it. I'll have to give this a try. Thanks!

Cool,

du -s -m /mnt/develop

shows 103Mb of things stuffed into the 37Mb squashfs image..... any idea how it came out on cramfs ?

Anyway, looks good.... now if only we had 'designer' on there too

- Andy

One apparent problem I've found is that tmake will write the paths for uic and moc in the Makefile as $(QTDIR)/bin/uic and $(QTDIR)/bin/moc. The QTDIR variable, by default, points to /home/QtPalmtop. However, for the dev_img, uic and moc are in (mount dircectory)/bin.

Two possible solutions are to:

1. add links for uic and moc to /home/QtPalmtop/bin

2. use "QTDIR=(mount_directory) make" to compile

I prefer the second option, but when I tried it, it included a file which caused the following error:

I haven't really looked into this much yet, so I may just be overlooking something.

- ashikase
anpachi, gifu, japan

Did you run compiler_setup.sh script? It should have created all nessesary links. At least I was able to build my Alarm Clock application with a fresh setup...

It was more than 50 Mbytes



Actualy I thought about it myself... maybe later

Has anyone installed on SL-5600?

You'll definetli need kernel module from this tread.

Now that I've got 'Dev_Img-1.6' running on my C3000....

Could someone tell me what command(s) you use to compile QT apps using 'dev_img-1.6' ?

Thanks,

Mark

is the generic code I've used for a lot of stuff

Stu

Thanks for your help, Stubear!

Mark

Don't forget to create a 64 or even 128 Mb swap file if you're planning to build relatively complex Qtopia GUI sources.

Thanks, Maslovsky.

Even though I am using a C3000 you recommend doing this?

Mark

ArchiMark, did you use the squashfs module that I posted to the 3000 forum for this? If by any chance you did then let me know and I will turn it into a proper IPK for 3000 users. I haven't had any responses on that thread as to its stability etc. yet. If not then I'll test when I finally get my 3000.

Cheers,

Andy

Sorry, Andy, but I think I used squashfs module posted by other forum member, m-morino....

Mark

OK ArchiMark, that doesn't bother me as much as people needing the feature and not being able to get hold of it.

If there's an IPK for the 3000 already then that's cool.

If not I will build one when I get my 3000 and have done some testing.

Glad you are up and running anyway,

Andy

Ok might be a basic question, but why do the instructions specify to relogin as zaurus?

Also why not just use "/home/zaurus/develop" as the mount point? Why make a link from another location?

Thank you,
Kerensa

This is really impressive, but I am missing a debugger (gdb), or am I missing something?


Andrew

gdb has traditionally always been installed as a seperate package. It's not useful to people that don't have debugging experience that are just doing a minor port so I can see the rationale here.

Check out the ELSI and you should find a version of gdb with gdb-server on there. Take note though, single step is a bit quirky and tends to hop backwards in the source even when you are tracing source line to source line... never had a good response as to why this happens.

- Andy

It will be very nice to have a full developer environment on the Zaurus.
But since I have a C3000, I have some questions for the people who tried this image:

Does the installation have any problems with the c3000 RAM/HD structure? In other words, do I have to create any symlinks to ensure proper functionality?
Is it possible to install the developer environment without the use of squashfs? Since the c3000 has enough disk space, this might enhance the speed.

thanks,
BramK

If I'm going to write some QT programe on Z, is this Dev. Img. 1.6 or zgcc better?
thx

Dev_Img-1.6 has a lot more goodies in it....

HTH,

Mark

ok, i decided to try dev_img 1.6 out, but run into some problem

I hv put the files "dev_img-1.6" & "image_setup.sh" in root of SD card
then I mkdir /mnt/card/mntpt

when I ran ./image_setup.sh /mnt/card/dev_img-1.6 /mnt/card/mntpt
it gives me error

*********
Setting mount point /mnt/card/mntpt...
ln: /mnt/card/mntpt/develop: Operation not permitted
Mounting image /mnt/card/dev_img-1.6...
Failed to munt image /mnt/card/dev_img-1.6 on /mnt/card/mntpt
*************

what seems to be the problem?
I am using Cacko 1.22a on a 860,
and it says cacko 1.22 support squashfs, so i don't need to install anything else, right?

thank you

hmm... ok....
I think may be I shouldn't have mkdir the mount-point directory...
b/c without mkdir b4 setup, it works...

can someone explain to me why? plz

thx