From Navit's Wiki
Revision as of 08:05, 21 March 2013 by Woglinde (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


Since 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

This guide assumes you already have the source downloaded locally, and have already built a package for Android using CMake (see Linux development).

  • Install Eclipse
    • Unzip to directory of your choice
    • Start Eclipse by going into your eclipse folder, and running eclipse
    • Setup a new workspace when prompted
  • Import Navit
    • File -> New -> Project...
    • Android -> Android Project
    • Next
    • Project Name: -> NavitProject
    • Create project from existing source
    • Location: browse to the directory navit/android/ within your cmake build directory.
    • Next
    • Build Target -> check Android 2.2
    • Next
    • Finish
    • Project -> Properties
    • Java Build Path from left hand window
    • Libraries tab
    • Add JARs
    • NavitProject -> libs -> TTS_library_stub.jar. OK
    • Java Compiler from left hand window
    • Apply on message window
    • Compiler compliance level: -> 1.6
    • OK
    • Yes

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?