Difference between revisions of "Projects/Marble/MaemoEnvironment"

Jump to: navigation, search
(Created page with '=== Maemo SDK / Scratchbox Setup === Developing for Maemo based devices does not mean to write software and compile on the device itself. Most of the development happens on norma...')
 
m (Text replace - "</code>" to "</syntaxhighlight>")
 
(4 intermediate revisions by 2 users not shown)
Line 5: Line 5:
 
=== Compiling Marble ===
 
=== Compiling Marble ===
 
To strip down the number of dependencies, we will use the Qt-based version of Marble. The compilation requires cmake as the build system and Qt development libraries. Make sure both are installed:
 
To strip down the number of dependencies, we will use the Qt-based version of Marble. The compilation requires cmake as the build system and Qt development libraries. Make sure both are installed:
<code bash>
+
<syntaxhighlight lang="bash">
 
[sbox-FREMANTLE_X86: ~] > apt-get install cmake libqt4-dev
 
[sbox-FREMANTLE_X86: ~] > apt-get install cmake libqt4-dev
</code>
+
</syntaxhighlight>
  
 
With the necessary dependencies in place we proceed to the next step, checking out the Marble source code.
 
With the necessary dependencies in place we proceed to the next step, checking out the Marble source code.
<code bash>
+
<syntaxhighlight lang="bash">
 
[sbox-FREMANTLE_X86: ~] > mkdir -p ~/marble/{src,build}
 
[sbox-FREMANTLE_X86: ~] > mkdir -p ~/marble/{src,build}
[sbox-FREMANTLE_X86: ~] > svn co svn://anonsvn.kde.org/home/kde/trunk/KDE/kdeedu/marble ~/marble/src
+
[sbox-FREMANTLE_X86: ~] > git clone git://anongit.kde.org/marble ~/marble/src
</code>
+
</syntaxhighlight>
  
 
Once all files were downloaded, prepare the compilation step:
 
Once all files were downloaded, prepare the compilation step:
<code bash>
+
<syntaxhighlight lang="bash">
 
[sbox-FREMANTLE_X86: ~] > cd ~/marble/build
 
[sbox-FREMANTLE_X86: ~] > cd ~/marble/build
[sbox-FREMANTLE_X86: ~] > cmake -DQTONLY=Yes ../src
+
[sbox-FREMANTLE_X86: ~] > cmake -DQTONLY=ON ../src
</code>
+
</syntaxhighlight>
  
The first cmake call may fail because of a missing qtdesigner dependency. At the time of writing, the qt4-designer package is broken. As a workaround, remove the ${QT_QTDESIGNER_INCLUDE_DIR} line in ~/marble/src/src/tilecreator/CMakeLists.txt and re-run the cmake command.
+
If cmake finished successfully, compile and install Marble:
 
+
<syntaxhighlight lang="bash">
Once cmake finished successfully, compile and install Marble:
+
<code bash>
+
 
[sbox-FREMANTLE_X86: ~] > make install
 
[sbox-FREMANTLE_X86: ~] > make install
</code>
+
</syntaxhighlight>
  
 
=== Running Marble ===
 
=== Running Marble ===
 +
Some maps have to be created at the first start of Marble. Currently this is not supported for Maemo. You can copy the files from another system or start up with a map like OpenStreetMap which does not need data creation. The latter is accomplished as follows:
 +
<syntaxhighlight lang="bash">
 +
nano -w ~/.config/kde.org/"Marble Desktop Globe.conf"
 +
</syntaxhighlight>
 +
Insert the following two lines (create the file and directory if they do not exist):
 +
[MarbleWidget]
 +
mapTheme=earth/openstreetmap/openstreetmap.dgml
 +
 
Execute the marble binary with the help of run-standalone.sh, a script provided by the Maemo platform to setup a working environment.
 
Execute the marble binary with the help of run-standalone.sh, a script provided by the Maemo platform to setup a working environment.
<code bash>
+
<syntaxhighlight lang="bash">
 
[sbox-FREMANTLE_X86: ~] > run-standalone.sh marble
 
[sbox-FREMANTLE_X86: ~] > run-standalone.sh marble
</code>
+
</syntaxhighlight>
 +
Marble should start up and become visible in Xephyr now. It will look like this: [[File:MarbleMaemoRouting.png]]

Latest revision as of 21:57, 29 June 2011

[edit] Maemo SDK / Scratchbox Setup

Developing for Maemo based devices does not mean to write software and compile on the device itself. Most of the development happens on normal desktop systems. A device like a N900 is indeed not needed: The scratchbox environment emulates it for you. Please follow the Maemo SDK Guidelines in the Maemo Wiki to setup scratchbox on your system. After package installation, follow the guide to start the SDK UI. You should end up with a scratchbox shell using the FREMANTLE_X86 target. Additionally, start the Maemo UI in Xephyr as described.

[edit] Compiling Marble

To strip down the number of dependencies, we will use the Qt-based version of Marble. The compilation requires cmake as the build system and Qt development libraries. Make sure both are installed:

[sbox-FREMANTLE_X86: ~] > apt-get install cmake libqt4-dev

With the necessary dependencies in place we proceed to the next step, checking out the Marble source code.

[sbox-FREMANTLE_X86: ~] > mkdir -p ~/marble/{src,build}
[sbox-FREMANTLE_X86: ~] > git clone git://anongit.kde.org/marble ~/marble/src

Once all files were downloaded, prepare the compilation step:

[sbox-FREMANTLE_X86: ~] > cd ~/marble/build
[sbox-FREMANTLE_X86: ~] > cmake -DQTONLY=ON ../src

If cmake finished successfully, compile and install Marble:

[sbox-FREMANTLE_X86: ~] > make install

[edit] Running Marble

Some maps have to be created at the first start of Marble. Currently this is not supported for Maemo. You can copy the files from another system or start up with a map like OpenStreetMap which does not need data creation. The latter is accomplished as follows:

nano -w ~/.config/kde.org/"Marble Desktop Globe.conf"

Insert the following two lines (create the file and directory if they do not exist):

[MarbleWidget]
mapTheme=earth/openstreetmap/openstreetmap.dgml

Execute the marble binary with the help of run-standalone.sh, a script provided by the Maemo platform to setup a working environment.

[sbox-FREMANTLE_X86: ~] > run-standalone.sh marble

Marble should start up and become visible in Xephyr now. It will look like this: MarbleMaemoRouting.png


This page was last modified on 29 June 2011, at 21:57. This page has been accessed 2,272 times. Content is available under Creative Commons License SA 3.0 as well as the GNU Free Documentation License 1.2.
KDE® and the K Desktop Environment® logo are registered trademarks of KDE e.V.Legal