Re: Developing on the N900 itself ?
 

It seems they have removed the stable repository :( I'm still having problems with that deb file - apt-get dist-upgrade always flags it up even though it is already installed.. and my SDK in general just doesn't seem to be working properly. I must be missing something, but no idea what..

If I can bring myself to installing everything one more time, I'll try again later on today and use the policy-rc.d fix instead.

Re: Developing on the N900 itself ?
 

I can confirm the exit 101 trick works; it also seemed to take less time to download and install all the binaries this time; only around 2 hours, though this may have been coincidence!

Here's the full list of commands to run to get from qole's image to a working sdk (plus a lot of patience), please note that you will need 7zip installed (apt-get install p7zip-full). I'm also assuming the image is in /home/user/MyDocs and you will also need to replace <your token code here> with the code you receive when agreeing to the license agreement at http://tablets-dev.nokia.com/eula/index.php

Oh, and you may also need to run these commands as root because of creating the /floppy and /sdk directories. I did it as root by default so can't be sure.

Re: Developing on the N900 itself ?
 

Many thanks to qole and Tigerite. Things went very smoothly by following all suggestions through qole's last post, and Tigerite has consolidated them nicely.

Anyway, the problem for me has always been making changes that require the rerunning of autoconf and/or automake. I've had some luck by soft linking stuff (i.e. automake1.8 -> automake, not automake1.4 -> automake), but generally, I have to bootstrap these kind of changes in scratchbox, and then copy the project over.

So, it would be the ultimate cool if someone had a recipe for properly installing and configuring the auto build stuff.

But again, qole and Tigerite rock the house.

Re: Developing on the N900 itself ?
 

Okay, I think I'll have to kill Nokia now; not only is the repository back up but there's a more up-to-date version so I've got to create my SDK all over again ;)

Re: Developing on the N900 itself ?
 

Hi can you plz tell if the "CHROOT=/floppy synchroot" is a cmd or it should be written in ld.so.conf? coz I put it in ld.so.conf file and I was getting "ldconfig: /floppy synchroot is not a known library type" however the installation completed without any errors. Thanks

EDIT: OK my bad.. got it. Thanks.

Re: Developing on the N900 itself ?
 

Glad you figured it out :) I can confirm that the commands I posted are also relevant for the new SDK rootstrap image, i.e. you still need to create the same directories and copy the same files, no more and no less.. there's a little bit of work involved to create your own .ext2 image from the tgz'd image, though (until qole is kind enough to host one - I would do it myself but I'd have to use something like RapidShare, which I loathe).

Re: Developing on the N900 itself ?
 

Installed the basic version of the rootstrap you posted qole, but the link to the more advanced one seems borked. Any chance you could put it back up again?

Re: Developing on the N900 itself ?
 

For users who have an existing SDK environment wouldn't it be enough to tar the contents of /scratchbox/users/mohammad/targets/FREMANTLE_ARMEL ?

Re: Developing on the N900 itself ?
 

If I understand things correctly, when working in any scratchbox target, some of the tools are cleverly redirected to x86 binaries. Look at /scratchbox/users/mohammad/targets/FREMANTLE_ARMEL/scratchbox. I think it's a soft link to /scratchbox.

EDIT:

Scratch that. /scratchbox is bound to /scratchbox/users/mohammad/scratchbox. No soft link.

Re: Developing on the N900 itself ?
 

Thanks for the reply. By new SDK do you mean maemo-sdk-v1_2.img.ext2.lzma from qole? coz this is what I have and dpkg -l | grep qt doesn't return anything. Also dpkg-buildpackage -b says Perl: warning setting locale failed, however the process goes on but this message keeps popping. Thanks