From Navit's Wiki
Revision as of 22:07, 9 October 2011 by Tryagain (talk | contribs)
Jump to: navigation, search

Install latest eclipse version with at least cdt-c/c++ support 6.0.1/2


After first start choose your workspace

And and install the svn-plugin

german howto [2]

english howto [3]

Add and install the autotools-plugin


With eclipse 3.7(helios) linuxtools and autotools support can be install either from market menu or the software install menu.

Import existing and new svn co (unfornatly the svn wizard has some problems with the navit repo so we are doing in with file import)

checkout the project via commandline into your workspace folder

svn co

make a new Project with File/New/Project

choose in the wizard c/c++ c-project

choose now GNU Autotools(if there is nothing under toolchains install autotools(autoconf,automake/gettext) via your os packagemanager) for Projektname choose the dir were you checked out the navit source eclipse will give a warning that the projectfolder exist ignore it and hit finish

eclipse will run the script and when its finished it should show Binaries and Archives, where you can run the navit exe

Doing Navit/Android development with Eclipse INCOMPLETE

You'll need an Eclipse installation with JDT plug-in. Plug-in itself can be downloaded from the Help->Install new software. Use the Programming Languages subcategory of the Indigo repository. Please be patient if you see a "Pending" message instead of available packages list.

Then install ADT plug-in as described at

Now start a new Android project/Create project from existing source, browse to location of AndroidManifest.xml in navit/android/ folder of your CMAKE build directory tree.

Use build target Android 2.2. You'll get a warning about minSDKVersion being 3, ignore it. If you specify lower target version, you'll get a error on android:installLocation.

In Project Properties, on Libraries tab of 'Java build path' subpage, click "Add JARs" and select TTS_library_stub.jar from libs subfolder of the project. Java Compiler subpage of Project properties, select Compiler compliance level of 1.6 (default 1.5 is too low because of @Override changes for generics adopted in 1.6).

And then the project should be clean of errors besides the only one stating that android_layout_default.xml is not well-formed. That's sad true. That file is indeed not an xml document but a fragment of one. Do we have some setting to switch this check off? Should we rename that file?