Difference between revisions of "Linux development"

From Navit's Wiki
Jump to: navigation, search
m (moved Navit SVN installation on Linux to Linux: Make autocomplete easier, keep links short and specific, unify OS articles)
(fix link)
Line 64: Line 64:
= Configuring the beast =
= Configuring the beast =
This is [[Configuring Navit|an entirely different matter]], young padawan. Good luck :)
This is [[Configuration]], young padawan. Good luck :)
You can also check a [http://www.len.ro/2009/07/navit-gps-on-a-acer-aspire-one/ post describing a Navit configuration on Ubuntu Jaunty].

Revision as of 19:34, 20 December 2012

Taking care of dependencies


Getting Navit from the SVN repository


cd ~ 


svn co https://navit.svn.sourceforge.net/svnroot/navit/trunk/navit/ navit





mkdir navit-build
cd navit-build

Once inside the build directory just call the following commands:

cmake ~/navit

Note: CMake will autodetect your system configuration on the first run, and cache this information. Therefore installing or removing libraries after the first CMake run may confuse it and cause weird compilation errors. If you install or remove libraries/packages (for example because the first CMake run complained about them missing), always do a clean CMake run:

 rm -r ~/navit-build/*
 cmake ~/navit

Running the compiled binary

The binary is called navit and can be run without arguments:

cd ~/navit-build/navit/


GNU autotools

Go to the directory where you checked out the svn repository:

cd navit

Start the make dance:

./autogen.sh && ./configure && make


Running the compiled binary

Here, I am skipping the usual "make install" (in my case, "sudo checkinstall make install") step, because I don't care about installing navit systemwide. I run navit directly from its svn folder, and it makes things much simpler (and safer).


cd ~/navit/navit/

Updating SVN


svn up


Prebuild binairies

Prebuilt binaries exist for many distributions.

Configuring the beast

This is Configuration, young padawan. Good luck :)
