Changes between Version 24 and Version 25 of android

Timestamp:

Feb 2, 2013, 11:51:23 PM (13 years ago)

Author:

Martin Kolman

Comment:

--

android

@@ -156 +156 @@
 }}}
 === Qt Components ===
-There are at least two Android ports of Qt Components.
-
-The koyinings one based on the Symbian Qt Components:
-{{{
-https://gitorious.org/~koying/qt-components/android-qt-components
-}}}
-And the one that is based on MeeGo Qt Components by Filip Brcic:
-{{{
-https://qt.gitorious.org/~brcha/qt-components/qt-components-android
-}}}
-
-I've been able to successfully compile both component sets. As my applications are using the MeeGo based components on Fremantle & Harmattan, I'll start with those.
-
-==== Compiling Qt Components with Necessitas ====
+There are at least three Android ports of Qt Components.
+
+The modified Ineans Qt Components:[[BR]]
+[https://qt.gitorious.org/~martink/qt-components/martinks-ineans-qt-components/commits/android]
+
+The koyinings one based on the Symbian Qt Components:[[BR]]
+[https://gitorious.org/~koying/qt-components/android-qt-components]
+
+And the one that is based on !MeeGo Qt Components by Filip Brcic:[[BR]]
+[https://qt.gitorious.org/~brcha/qt-components/qt-components-android]
+
+I've been able to successfully compile both component sets. As my applications are using the !MeeGo based components on Fremantle & Harmattan, I'll start with those.
+
+
+==== Compiling Qt Components with necessitas ====
+The modified Inens Qt components are based on both the Inneans Fremantle component port & Martin Kolmans changes for BB10 support. These components use the familiar Fremantle & Harmattan import syntax:
+
+{{{
+import com.nokia.meego 1.0
+}}}
+
+So it is possible to reuse code from Fremantle & Harmattan (and BB10 project using these components) without having to rewrite the import statement.
+
+First clone the components and then switch to the ''android'' branch:
+
+{{{
+git clone git://gitorious.org/~martink/qt-components/martinks-ineans-qt-components.git
+cd qt-components-android
+checkout android
+}}}
+
+The export path to the Necessitas Qt libraries to compile against:
+
+{{{
+export QTDIR=<path to the Necessitas SDK>/Android/Qt/482/armeabi
+export PATH="$QTDIR/bin:$PATH"
+}}}
+
+'''NOTE:''' Check out the Qt version in your Necessitas SDK version, it might not be exactly 482 (Qt 4.8.2) but older or newer.
+
+Then configure the components for building:
+{{{
+./configure -fremantle -no-maliit -make cssu -force-local-theme -mobility -no-xrandr -no-xdamage -nomake examples
+}}}
+
+And build them:
+
+{{{
+make -j 5
+}}}
+
+Once the build is finished, the results are available in the ''imports'' folder. Just move it somewhere to your Android device or inside your application package and set the ''QML_IMPORT_PATH'' environmental variable to point where the folder is located.
+
+'''Modifineg the components'''
+For some reason, the source code is present in multiple copies (probably because of of how the SSU/CSSU versions were patched from the upstream Qt Components ?). Anyway, if want your modifications to the source code to take effect once reconfigured & recompiled, edit the files in ''src/fremantle/cssu/''. Modifing the others has no effect on the components that are actually built using the configure options described above.
+
+
+==== Compiling Brchas Qt Components with Necessitas ====
 
 Clone the android Qt Components Git repository and make sure you are on the android branch: