Sorry, it took me a bit of time to make the tests:
A simple "Hello world" project runs correctly in Qt Creator?
When using the external lib, the program crashes. I suspect an incompatibility of this old lib with Windows 10.
I need to further investigated this issue...
Well, I consider to remove/change the code in my qt app to not depend on qtwebengine... It just displays some wheather maps (images) from an online source. I think I can realize that by fetching those images somehow from that online source and display them on an QLabel or so. I think qtwebengine is quite an overkill for that :)
Thanks for the reply. Indeed you are wright. It is very easy actually. I just compiled qt4.8.6 for my system. Then I found the sqlite project in sqldrivers. Compiled this library for my system, copied it and it works!
Very easy. Learned again a lot!
Thank you all for the great support!
Ok, thanks for the reply. It pointed me in the correct direction and after many failures I finally figured it out.
I guess you only learn when you need to dig deep.
The only thing I had to do was install the correct version of openSSL. Since it is my first time I had no idea what the letter actually meant, I picked the first build, which was version g, I had to install version n.
For all future wanderers, the only thing you need to do to make the client work is one of the two options:
Just copy ssleay32.dll and libeay32.dll to working directory OR
Install the latest version and set PATH to the folder where the two dlls are located.
After that you can use QWebSocket without even knowing SSL exists. Just call:
Did not work with Firebird 3.0.3 embedded without a running server or firebird.exe -a. It just started to work as a real embedded database and not a tcp based connection when using an empty hostName. Instead of:
For normal web browsing that would be sufficient, yes.
In my case we use a web-driven GUI. If I stop the script that needed too long (due to some network error or whatever) the GUI is missing on the device.
When you dont have
uSocket = new QUdpSocket(this) ;
as uSocket just point to random location. (dangling pointer)
QByteArray *priPackNuser; <<< also just a pointer.
You should do ( as @SGaist mention)
( no *, means its real bytearray, not a pointer to one)
So you change it from heap allocation to stack allocation.
If you dont change to non pointer then you need
QByteArray *priPackNuser = new QByteArray ;
as else its a dangling pointer too!
But no need for pointer to QByteArray here.
i replied myself.i found problem .when my app is compiled with emulator,this errors is returns when emulators that have the Use Host GPU setting ticked*
if Try turning that off, you'll no longer see those warnings (and the emulator will run horribly, horribly slowly..)
but we have not this warning.
In my think those warnings are harmless. Notice that the "error" is EGL_SUCCESS, which would seem to indicate no error at all!