Re: Navit on N900
 

No problem, you're very welcome!

Thanks to gianko for helping- two remarks from my side:

1. Directories with a point in front like "/home/user/.navit" are so called hidden directories, you won't see them in some gui-based filemanagers unless you disable the hide-function. In the build-in you have basically only access to MyDocs if I remember correctly. So the solution is to mv the files like described out of xterm.

2. When you are in xterm anyway, you can type "navit" afterwords and see what happens. It is always a good trick to do so with any program that makes trouble because there are helpful outputs in xterm like "error-cannot find blabla... " etc. that you don't see when launching it from an icon.

HTH and good luck! Please feel free to report back!

CU Michael

Re: Navit on N900
 

I built navit against qt4 in the fremantle sdk

[sbox-FREMANTLE_ARMEL: ~] > apt-cache policy libqt4-gui
libqt4-gui:
Installed: 4.7.0~git20100909-0maemo1+0m5
Candidate: 4.7.0~git20100909-0maemo1+0m5
Version table:
*** 4.7.0~git20100909-0maemo1+0m5 0
500 http://repository.maemo.org fremantle/sdk/free Packages
100 /var/lib/dpkg/status
4.6.2~git20100401-0maemo1+0m5 0
500 http://repository.maemo.org fremantle/sdk/free Packages
4.6.2~git20100310-0maemo1+0m5 0
500 http://repository.maemo.org fremantle/sdk/free Packages
4.5.3~git20090723-0maemo6+0m5 0
500 http://repository.maemo.org fremantle/sdk/free Packages
4.5.3~git20090723-0maemo4+0m5 0
500 http://repository.maemo.org fremantle/sdk/free Packages
[sbox-FREMANTLE_ARMEL: ~] >

I upgrade to the qt4 version in CSSU for the next build.

I myself use the internal GUI right now.

Rainer

Re: Navit on N900
 

i always download both the new navit.xml and my customized one to my local computer and comapre them with a GUI diff (like meld or kdiff3) -- that way i

- see how much changes are there
- see which changes i need to adopt (eg maps configuration remains always in maps.xml, locale attribute is usually missing, ...)
- can easily copy changes over and may even change them if necessary

afterwards i simply move the new navit.xml back to /home/user/.navit/

Re: Navit on N900
 

I'm looking forward to test this and would be thankful for a short announce here in the thread.
Out of curiosity: Is the qt-painter/qml so much smoother/faster than internal? Never seen it working...

Tnx & Bye

CU Michael

Re: Navit on N900
 

I will post here when I updated qt to cssu. The build I just uploaded still comes with the old qt4 variant.

I try to build once a month, typically end of a month or beginning of the next month.

Re: Navit on N900
 

ceterum censeo:
could you possibly share how you build? i try to setup QtSDk/MADDE so it builds navit for maemo (and packs) but it's a rather frustrating experience ...

Re: Navit on N900
 

From memory (I try to provide something more detailed at the weekend, but cannot promise that I manage to write it down):

You should be able to download the sources including the debian dir from bokomoko.de (just use deb-src in sources.list). This should build out of the box on the x86 target. On the armel target, one package does not build, because a binary fails on qemu. This is a know problem in the armel build setup inside scratchbox (and also the reason, why navit is not in the extra repository). Fortunately, it is the navit_data package which is architecture independent and I can simply take the package from the x86 build. Also make sure that you have freetype from CSSU or my libfreetype-navit package.

Hope that helps somewhat,
Rainer

Re: Navit on N900
 

nja, not really ;-)
i was aiming at a lower level: i never really managed to get scratchbox up and running so it would build navit.

any pointers to how it is done, would be highly appreciated

Re: Navit on N900
 

The wiki contains detailed documentation on setting up scratchbox. If you do not run Ubuntu or Debian, I would setup a VirtualBox image with Ubuntu or Debian:

http://wiki.maemo.org/Documentation/...K_Installation

Re: Navit on N900
 

been there, done that, didn't work.

but now that MoNav supports street names, i am ready to switch.
takes some time to prepare a map, but
- routing is much faster
- much better
- interface is much easier to handle (most notably looking up street names when there's more than one street with the same name)