@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.

@Randomator Sir, download the Qt Sources, e.g current the sources available are qt-everywhere-opensource-src-5.5.1, After extracting cd C:\qt-everywhere-opensource-src-5.5.1\qtbase\src\plugins\sqldrivers\mysql then make sure you call qmake from Qt5.5, for this purpose you can type the complete path of the qmake. then use make and make install. I hope it will help you.

@SaundersB Would you be able yo share the sample code as to how you managed to solve this issue? I tried for 2 days now and the only working solution I found was to copy the QT dlls to my project. Regards Dariusz

Hi! I am trying to compile Qt 5.x for Windows Mobile 6.5, and getting a lot of errors about wcsftime and other functions told above. How did you solve that problems?

@mrjj ROFL! The function call was before setupUI ^.^ I'll see if that fixes it :P Edit: Yep! That was the problem :P My bad! Thanks for the help!

Both your classes need to inherit from QObject for the signal/slot mechanism to work. Code blocks are either preceded by 4 spaces (good for one liners): int variable; or they can be enclosed by `` ` (triple back ticks, good for inline elements and longer blocks): #include <iostream> int main (int argc, char * argv[]) { std::cout << "Hello, World!\n"; } Google Markdown syntax for some more markup details.

@swhweng Well, you would need to implement the POSIX standard (or at least parts of it) on FreeRTOS. This is, for sure, a very complex task :-)

I have same problem with GST, but in 0,1 version. GST launch working, but Qt cannot find m_videoSink, even modify qgstreamervideowindow.cpp doesn't work.

@SGaist Thanks for the reply . I just noticed that i mixed dlls . I used windeployqt as you mentioned and i found all the dependencies . additionally i added these Dlls. libgcc_s_dw2-1.dll libstdc++-6.dll libwinpthread-1.dll

I figured it out. I needed to set my QObject and QCore stuff properly. In the .pro file of the shared library, I added: QT += core In the shared library's .h file, I switched this: class CTSCANSHARED_EXPORT ctScan { public: ...blah blah... with this: class CTSCANSHARED_EXPORT ctScan: public QObject { Q_OBJECT public: ...blah blah... And then ensured the shared library's .h file had this: #include <QObject> And then it compiled properly.

I have solved the issue using the following post: https://forum.qt.io/topic/49710/solved-first-steps-and-mysql/10

Hi and welcome to devnet, To discuss such matters, I'd recommend posting on the interest You'll find there Qt's developers/maintainers (This forum is more user oriented)

Another interesting development: I tried running on another machine with the Qt toolchain installed, and the program worked. So it appears it is still reading something from the filesystem that is not on a regular Windows machine, but I don't know what that might be. I did package all the qmldir files needed for Qt Quick to work.

Thanks, that should do it!

By the way, I found that the Intel Core 2 Duo CPU T7500 is a 64 bits one. I have installed Ubuntu 32 bits because there was no added value for me to install a 64 bits one. for some compatibility reasons I kept also a 32 bits one when I started to use Ubuntu 4 years ago Do you think that it could potential be the source of the problem or it doesn't matter?

Hi, It depends partly on what you use on your board, do you have a X server running ?