Projects/Mobile/Scratchbox: Difference between revisions

From KDE TechBase
(There will be more info about scratchbox coming)
 
(2 intermediate revisions by the same user not shown)
Line 17: Line 17:


= Known issues and oddities =
= Known issues and oddities =
== Linker fails when using CPU transparency ==
If the linker doesn't find your libs for no good reason, you should add the following parameter when calling cmake to create the build dir:
-DCMAKE_CXX_LINK_FLAGS=\"-Wl,-rpath-link,/lib -Wl,-rpath-link,/usr/lib -Wl,-rpath-link,/usr/local/lib ...\"
(here the "..." means that you have to add one "-Wl,-rpath-link,/foo/lib" for each folder where the linker might need to look for libs)
== Random segfaults or build hang using CPU transparency ==
In some cases you could experience crashes at build time coming from qdbusxml2cpp. The reasons are rather unclear so far but seem to be related to the linker. Current investigations indicates that it happens if your build is using "-g -O2" (or higher value for -O). If you're using any of the -g or -O options alone you should be fine.

Latest revision as of 07:56, 31 May 2010

This page is for collecting information about getting KDE running on the Maemo platform used by the Nokia mobile devices N800, N810 and N900.

Getting a SDK

Maemo5 and the N900

Older releases (mainly Diablo and N810 related)

Known issues and oddities

Linker fails when using CPU transparency

If the linker doesn't find your libs for no good reason, you should add the following parameter when calling cmake to create the build dir:

-DCMAKE_CXX_LINK_FLAGS=\"-Wl,-rpath-link,/lib -Wl,-rpath-link,/usr/lib -Wl,-rpath-link,/usr/local/lib ...\"

(here the "..." means that you have to add one "-Wl,-rpath-link,/foo/lib" for each folder where the linker might need to look for libs)

Random segfaults or build hang using CPU transparency

In some cases you could experience crashes at build time coming from qdbusxml2cpp. The reasons are rather unclear so far but seem to be related to the linker. Current investigations indicates that it happens if your build is using "-g -O2" (or higher value for -O). If you're using any of the -g or -O options alone you should be fine.