Mobile and Embedded

Hi ariacorrente, happy to read you on this forum ! Thanks for your help (SGaist also !). For the moment i'm just trying to cross compile QT5 on linaro ubuntu (not udoobuntu) like the tutorial explain. If i will have a success i will try another time on udoobuntu !

Hi, I am sure the problem is simple: You create the statemachine as local variable in the constructor. This means, when the constructor exists, the state machine is destroyed. make it a member of the class.

You can go the QML way for the gui, you have examples in Qt's documentation for video playback. The interrupt part is lower level programming you'll need to write some code for that yourself. As for the keyboard, you could use the CLKeyboard qml keyboard

Update. The Android debugger bug appears on another developer's PC (Windows 7 x64). The bug is in Qt Creator itself, not in the framework: Qt Creator 3.1.1 (from Qt 5.3.0) works even with newer Qt 5.3.2 and latest Android NDK/SDK. The bug is NOT fixed in Qt Creator 5.2.2 from Oct 13rd (http://download.qt-project.org/official_releases/qtcreator/3.2/3.2.2/)

Hi deweirdt, Sorry i never managed to get pass it, ended up using GDI instead due to time pressure. Mark

You're welcome, happy coding !

Seeing only assembler code generally means that one tries to debug a release build

Thank you Gene! I will re-configure to use API 15. I am building on a 64-bit Ubuntu 14.04 LTS host. I started over building Qt 5.4.0 for Linux 64-bit. I figured if I failed at building Qt Linux I should not even try building Qt Android. After installing many additional dependencies the build finally succeeded. I am getting many missing header files when I configure to build Qt 5.4.0 for Android. I expect I need to install all the 32-bit package equivalents of the 64-bit packages I had to install to build Qt 5.4.0 Linux for 64-bit. Would it be easier to build Qt Android under a 32-bit Linux host rather than a 64-bit Ubuntu 14.04LTS ? I have already run into problems simply trying to build 32-bit and 64-bit Qt apps under the same 64-bit Ubuntu. The mesa OpenGL 32-bit and 64-bit packages do not like to install side-by-side and the last one installed wins. I am concerned there may be other 32-bit/64-bit devel packages that may not play well together. Thank you for your help, -Ed @ #!/bin/bash See: http://qt-project.org/wiki/Qt5ForAndroidBuilding /usr/lib/jvm/java-6-openjdk-amd64 /home/edward3/android/sdk /home/edward3/android/android-ndk-r10b export JAVA_HOME=/usr/lib/jvm/java-6-openjdk-amd64 export ANDROID_SDK_ROOT=/home/edward3/android/sdk Qt uses AccessibilityDelegate was introduced in Android SDK API 14 so try using SDK API 14 or greater. export ANDROID_API_VERSION=android-15 export ANDROID_BUILD_TOOLS_REVISION=17.0.0 export ANDROID_NDK_ROOT=/home/edward3/android/android-ndk-r10b ./configure -v -xplatform android-g++ -nomake tests -nomake examples -android-ndk ${ANDROID_NDK_ROOT} -android-sdk ${ANDROID_SDK_ROOT} -android-ndk-host linux-x86_64 -android-toolchain-version 4.8 -android-ndk-platform android-10 -skip qttranslations -skip qtwebkit -skip qtserialport -skip qtwebkit-examples -no-warnings-are-errors echo "Configure Done" @

-How did you implemented the video surface? Did you specified which format do you want to receive?- Are you "unmapping":http://qt-project.org/doc/qt-5/qvideoframe.html#unmap the frame after using it?

my add-on issue solved by http://qt-project.org/forums/viewthread/46640/

SGaist, your help here has solved my issue that you've been looking into - allowing me to move on to the next few issues :)

k sir,,,sorry

You should rather do out of source builds, so if something goes wrong you can just delete the whole thing and start over without having to clean the sources. If you (re)configured several times for compilation/cross-compilation without cleaning in between then you probably have a messed up build in there.

I thought that you needed to run it infinitely. So does it work now ? If yes then mark it as solved.

Take also look into this tpoic: http://qt-project.org/forums/viewreply/197653/ Pleople discuss Qt look & feel versus native look & fell there, which might be a big issue for Apple devices.

About the QML versus Widgets topic: My understanding is that Widgets are not under development anymore. They were targeted to desktop computers and they have been made available to mobile devices. Widgets will remain part of Qt in future, but the developers aare now focusing on QML. So don't expect new widgets or new widget styles. QML is under development a lot, new styles will get added as well as new input elements. However, nobody knows when we will be able to imitate the native look and feel completely. Progress is slow here, obviously slower than the native development kits evolve. As long Qt does not really USE the native dialog elements, it will never look 100% native - that's my opinion. This issue has also never been resolved completely on Linux and Windows. Qt has its own look and feel, and I dont expect that this will ever change in future. So we either have to accept that or dont Qt for the GUI. By the way: I had great success using Qt in the backend without GUI.