Difference between revisions of "Linux development"

From Navit's Wiki
Jump to: navigation, search
m (Usul moved page Linux to Linux development without leaving a redirect: precisie titles)
 
(11 intermediate revisions by 5 users not shown)
Line 2: Line 2:
 
See the [[Dependencies]] page for a list of software packages required to build Navit. To build with [[#CMake|CMake]] you will need '''CMake 2.6''' or newer.
 
See the [[Dependencies]] page for a list of software packages required to build Navit. To build with [[#CMake|CMake]] you will need '''CMake 2.6''' or newer.
  
= Getting Navit from the SVN repository =
+
= Getting Navit from the GIT repository =
 
First, let's make sure we are in our home directory: this is only for the sake of making this tutorial simple to follow. You can save that directory anywhere you want, but you will have to adapt the rest of the instructions of this guide to your particular case.
 
First, let's make sure we are in our home directory: this is only for the sake of making this tutorial simple to follow. You can save that directory anywhere you want, but you will have to adapt the rest of the instructions of this guide to your particular case.
 
  cd ~  
 
  cd ~  
  
Now, let's grab the code from SVN. This assumes that you have subversion installed.
+
Now, let's grab the code from Git. This assumes that you have git binaries installed.
svn co https://navit.svn.sourceforge.net/svnroot/navit/trunk/navit/ '''navit'''
+
  git clone https://github.com/navit-gps/navit.git
  
 
= Compiling =
 
= Compiling =
There are currently two methods of compiling Navit - using GNU autotools or using CMake. GNU autotools was the old method, but will become deprecated in favour of CMake.
+
GNU autotools was the old method but is removed in favour of CMake.
  
 
==CMake==
 
==CMake==
CMake builds Navit in a separate directory of your choice - this means that the directory in which the SVN source was checked out remains untouched.
+
CMake builds Navit in a separate directory of your choice - this means that the directory in which the Git source was checked out remains untouched. See also [[CMake]].
 
  mkdir navit-build
 
  mkdir navit-build
 
  cd navit-build
 
  cd navit-build
Line 21: Line 21:
 
  make
 
  make
  
'''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
+
'''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 (though installing new libraries should be ok). If you install or remove libraries/packages and subsequently run into errors, do a clean CMake run:
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/*
 
   rm -r ~/navit-build/*
 
   cmake ~/navit
 
   cmake ~/navit
Line 33: Line 32:
 
It is advised to just run this binary locally at the moment (i.e. not to install system-wide).
 
It is advised to just run this binary locally at the moment (i.e. not to install system-wide).
 
Note that for this to work, Navit must be run from the directory where it resides (that is, you must first change your working directory, as described above). If Navit is run from another directory, it will not find its plugins and image files, and will not start.
 
Note that for this to work, Navit must be run from the directory where it resides (that is, you must first change your working directory, as described above). If Navit is run from another directory, it will not find its plugins and image files, and will not start.
 
==GNU autotools==
 
Go to the directory where you checked out the svn repository:
 
cd '''navit'''
 
 
Start the make dance:
 
./autogen.sh && ./configure && make
 
 
It is better to use autogen and configure before make, due to the heavy flux of changes in the svn version. Also, putting them all in one command ensures that they go through the next step only if the previous step succeeded. In the end, hopefully, you get a fully compiled navit binary in the navit/ subfolder (so basically, it looks like ~/'''navit'''/navit/navit. Yeah.)
 
  
 
===Running the compiled binary===
 
===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).
+
Here, I am skipping the usual "make install" because we don't need to install navit systemwide for this example.
  
 
To execute navit, you can simply click on the binary file (if you are sure it is compiled properly) and it should launch. If you prefer to launch it from a terminal, you need to go into the directory containing the binary, first, like so:
 
To execute navit, you can simply click on the binary file (if you are sure it is compiled properly) and it should launch. If you prefer to launch it from a terminal, you need to go into the directory containing the binary, first, like so:
Line 50: Line 40:
 
  ./navit
 
  ./navit
  
= Updating SVN =
+
= Updating the GIT code =
  
You don't need to recompile everything to update navit to the latest SVN; with svn update only the edited files will be downloaded. Just go to the navit directory (e.g. /home/CHANGEME/navit) and run:
+
You don't need to recompile everything to update navit to the latest code; with 'git pull' only the edited files will be downloaded. Just go to the navit directory (e.g. /home/CHANGEME/navit) and run:
  
  svn up
+
  git pull
  
You then follow this by either the instructions in [[#CMake|CMake]] or in [[#make|make]]. Actually, with CMake you can miss out the step where you make the build directory - just use the old one. With make you can usually miss out the ''./autogen.sh'' and ''./configure'' steps.
+
You then only need to run "make" again from your binary folder ( navit-build in the cmake example, or the current folder when using autotools).
 
  
 
= Prebuild binairies =
 
= Prebuild binairies =
Line 69: Line 58:
  
 
[[Category:Ports]]
 
[[Category:Ports]]
 +
[[Category:Linux]]

Latest revision as of 06:27, 23 January 2017

Taking care of dependencies[edit]

See the Dependencies page for a list of software packages required to build Navit. To build with CMake you will need CMake 2.6 or newer.

Getting Navit from the GIT repository[edit]

First, let's make sure we are in our home directory: this is only for the sake of making this tutorial simple to follow. You can save that directory anywhere you want, but you will have to adapt the rest of the instructions of this guide to your particular case.

cd ~ 

Now, let's grab the code from Git. This assumes that you have git binaries installed.

 git clone https://github.com/navit-gps/navit.git

Compiling[edit]

GNU autotools was the old method but is removed in favour of CMake.

CMake[edit]

CMake builds Navit in a separate directory of your choice - this means that the directory in which the Git source was checked out remains untouched. See also CMake.

mkdir navit-build
cd navit-build

Once inside the build directory just call the following commands:

cmake ~/navit
make

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 (though installing new libraries should be ok). If you install or remove libraries/packages and subsequently run into errors, do a clean CMake run:

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

Running the compiled binary[edit]

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

cd ~/navit-build/navit/
./navit

It is advised to just run this binary locally at the moment (i.e. not to install system-wide). Note that for this to work, Navit must be run from the directory where it resides (that is, you must first change your working directory, as described above). If Navit is run from another directory, it will not find its plugins and image files, and will not start.

Running the compiled binary[edit]

Here, I am skipping the usual "make install" because we don't need to install navit systemwide for this example.

To execute navit, you can simply click on the binary file (if you are sure it is compiled properly) and it should launch. If you prefer to launch it from a terminal, you need to go into the directory containing the binary, first, like so:

cd ~/navit/navit/
./navit

Updating the GIT code[edit]

You don't need to recompile everything to update navit to the latest code; with 'git pull' only the edited files will be downloaded. Just go to the navit directory (e.g. /home/CHANGEME/navit) and run:

git pull

You then only need to run "make" again from your binary folder ( navit-build in the cmake example, or the current folder when using autotools).

Prebuild binairies[edit]

Prebuilt binaries exist for many distributions.

Configuring the beast[edit]

This is Configuration, young padawan. Good luck :)

You can also check a post describing a Navit configuration on Ubuntu Jaunty.