@dheerendra At this point, we are fairly certain that the problem is in the main thread code. I have uploaded the main thread code in the previous comment. Please suggest any necessary changes that could solve the issue. thank you.

If it's solved, Please set it to "Solved" from unsolved.

If you want to compile from source, you need to follow the steps described here: http://doc.qt.io/qt-5/build-sources.html

Thanks, I am trying this now.

The compilation completed successfully, after I had configured with -qt-xcb (otherwise there would be an issue with library xcb-sync).

Thanks @aha_1980 for the advices !

@jsulm there was in fact a problem with window3d() that MinGW didnt complain about! Thanks!
@JonB no I had commented out only up to the second screenshot, so that's why this was the problem.
And about the second issue, to be honest I adapted the constructor from an older version of the application and it also had &argc. At one point I also noticed it and now I tried out both and both work.

@JonB Do not misunderstand. I have not said that I will not try your solution. I have just explained my temporary approach that I'm currently using to find the origin of my crashes. For the future I will take time to investigate more with the hope to have a generic solution to apply on all my VS solutions.

@Kinesis No need to feel bad - I'm helping here voluntary :-)
I don't think you need to upload your code. If somebody has questions he/she can ask.

Remove the -j 8. The error is somewhere else. These are just warnings.

AFAIK, QtWebKit static build has been disabled a long time ago.

@Wael11
For anyone reading this: This is known behaviour, which I stumbled across a long time ago and it was infuriating.

With a QSpinbox Qt Internal code uses a timer on clicks/presses. If you step through in debugger you exceed the timeout and get bad/double behaviour.

Simplest: change all connect() to QSpinbox click/key to pass Qt::QueuedConnection as last parameter for connection type, not default Qt::DirectConnection. Now you can use debugger breakpoints and all will be well. I wrote a method to connect all my spinboxes like this.

@Punit
see the Spectrum example

Then do you mean: does Qt provide a way to read this tag ? Or are you looking for which widget can show the content once you got the data ?

QTableWidget already has an internal model otherwise it's a QTableView.

@the_ said:

I for myself do not like this format...

No-one does ^_^

Check in the ndk whether you have gcc 4.8 available IIRC there was a change with r11.

@mrjj said:

seems to be full screen/max ?
seems.
Well, if not used setgeometry, window open in left high angle.

@bogong For me it's normal develop qt (also for mobile application), but in this time I must develop a strange case, I must use a native controller (that it can't be emulate in qt/qml) and from this I must start the qml GUI. It's all ok, I see the qml elements but I can't catch the user interaction, not press button, nothing. I started from Qt project where I added native object-c files, AppDelegate, other native controller, etc.