The problem is solved,

The problem was caused by the difference between Qt SDK compiler and application compiler !

I recompiled the src of qt sdk with the compiler used to my program and now it work !
thanx,

I'm not sure anyone cares about this anymore, but I believe I know what the problem is.

When the plugin class is created, it is actually created outside the currently executing QApplication (via dlopen) and the code is running in a different thread. By reading up a bit on dlopen, it seems that the memory where the library is created comes from a different pool and that all libraries (used like this at least), should make sure to implement a function to destroy themselves.

Not sure if this makes any sense for someone, but it does for me.

Now, I just need to figure a way to get the libraries thread to join with the man QApplication that is already running.

@Ajith_P_V Yes that is right, you don't need to add the physical device. That was really just an extra option in case that was convenient to you later on : )

Have a look at creating kits for cross compiling in the qt docs if you can find it! - there are quite a few bits of info out there that may fill in the gaps I have left. I only gave the general steps required.

@Paul-H. D'oh! Why, of course, how silly of me. visibility: Window.AutomaticVisibility does NOT automatically do visible: true.

Truly a case of needing to ask someone else to realize you're making a rookie mistake. Thanks for your help, Paul.

This looks very promising, thanks ! :)

Hi,

Sure you can. One thing that you might use is a QProgressBar (with min and max at the same value so it's animated as in don't know how long it can take. Or you can use a gif in a QMovie object.

Good !

However, I'm not sure I'm following you on that one. Where did you put that resize ?

If you can't from the Topic Tools menu, then just edit the thread title and prepend [solved]

@Varius said:

thread = new QThread(this);
console->moveToThread(thread);

IIRC, these lines are doing more than you think they do. thread's parent is your object, then you move your MyObject instance to thread, so all objects who are child of your MyObject instance are moved the thread. So thread will be moved to itself.

All in all, you should rather have thread in your main as a stack object

17:49:59: Running steps for project AndroidTest02...
17:49:59: Configuration unchanged, skipping qmake step.
17:49:59: Starting: "C:\Qt\Tools\mingw491_32\bin\mingw32-make.exe"
C:\Qt\5.4\android_armv7\bin\qmake.exe -spec android-g++ -o Makefile ..\AndroidTest02\AndroidTest02.pro
Cannot find file: ..\AndroidTest02\AndroidTest02.pro.
makefile:196: recipe for target 'Makefile' failed
mingw32-make: *** [Makefile] Error 2
17:50:00: The process "C:\Qt\Tools\mingw491_32\bin\mingw32-make.exe" exited with code 2.
Error while building/deploying project AndroidTest02 (kit: Android for armeabi-v7a (GCC 4.9, Qt 5.4.1))
When executing step "Make"
17:50:00: Elapsed time: 00:01.

You're welcome !

Happy coding !