@Tapto said in DLL issue even with all Qt DLL in the directory:

=> But Qt 5.12.2 doesn't come with WinGW 32 bits.

Yes it does. https://blog.qt.io/blog/2019/03/15/qt-5-12-2-released/

=> No it doesn't work in Qt Creator either. In Qt Creator, I only get a message "Application crashed". I get the error code only when launching the executable manually.

The wiki page says, "This guide... assumes that... the release version of your app works correctly when you build + run it from Qt Creator".

If it doesn't work in Qt Creator, then it won't work when you try to deploy it.

As I said I am using 32bits external libs. Maybe the issue is with those libs. Could you give me a pointer on how to try to debug this?

Create a small Hello World project using Qt only. Does this run correctly in Qt Creator? Create a small project that uses your external lib. Does this run correctly in Qt Creator?

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 :)

@SGaist

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!

Just case: the latest version of Qt 4 is Qt 4.8.7.

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:

QWebSocket socket; socket.open( QUrl("someaddress") );

And, when the dlls are found the warnings disappear.

That's it.

@koahnig

You're right, I think I'll go for it.

Thx for your time et your help anyway.

@hskoglund thank you so much!!!
I import <QVarianList> and it solved my problem.

@Lasith
Instead of 100 use ui->tableWidget->rowCount().

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:

const QString hostName = "localhost";

just

const QString hostName = "";

That helped finally!

@Technologist
Which python and mingw version do you use?

Hi! You could install a custom message handler or force your application to die on warnings by defining QT_FATAL_WARNINGS.

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

These messages aren't critical, you can ignore them. What's important is, that you don't crash the application anymore.

The problem is the same as in your other thread: you need to take care of the destruction order of your qobjects.

Unplugging the tablet does not help. You have to at least temporarily disable the driver.
The issue is described in detail here: https://bugreports.qt.io/browse/QTBUG-47548

You can stop the driver like this: net stop WTabletServicePro
And restart the driver with this command: net start WTabletServicePro

@p3c0

Thanks a lot.

Oh well, I see http://doc.qt.io/qt-5/qspinbox.html

Signals void valueChanged(int i) void valueChanged(const QString &text)

<--rtfm! Its now clear to me :)

You're welcome !

Since you have it working now, please mark the thread as solved using the "Topic Tools" button so that other forum users may know a solution has been found :)

It works,

thanks a lot

@M4RZB4Ni said:

Hi
When you dont have
uSocket = new QUdpSocket(this) ;
then
uSocket->writeDatagram(xx
will crash.
as uSocket just point to random location. (dangling pointer)

Next:
QByteArray *priPackNuser; <<< also just a pointer.
You should do ( as @SGaist mention)
QByteArray priPackNuser;
( 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.

@mrjj

Your welcome,
it can be a pain to find answers at times, so having a guide near the IDE for odd errors helps in getting stuff done quicker for those odd errors

Thanks for your advise. I'll try it.

@Qinyx
Good work.

Last week i sent a "false positive" report to avast av and now looks like the MSVC2015-32bit package is not blocked anymore

@Chris-Kawa
Thank you :)

Thanks, it work !

@hskoglund Thank you very much, now it works. :)

Did you install MSVC2015 before or after Qt ?

Can you see it in the Compilers tab ?

Then I'd recommend taking a look the example code and rewrite yours to match it.

I solved this problem.

I just added this lines in my CMakeLists.txt

qt5_add_resources(QT_RESOURCES_CPP resources/qml.qrc) add_executable(my_app src/my_app.cpp src/my_app.h ${QT_RESOURCES_CPP}) target_link_libraries(my_app lib1 lib2 ...)

The problem was that I was adding my reference to QT_RESOURCES_CPP in the target_link_libraries(...) instead of add_executable(...). For some reason this didn't work properly.

Thank you,
Jonatan

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!
goodluck

finally i deleted

import QtGraphicalEffects 1.0 import QtMultimedia 5.0

now it worked and built successfully .

and apk file that i created.
http://www.mediafire.com/download/1zcylimkzj2idu2/spiralmyappcompiled4android.apk
thanks for attention

Hi,

Are you also using g++4.9 to build Qt ?

See https://forum.qt.io/topic/26395/how-to-solve-issue-cannot-find-lgl-in-qt5-installed-in-ubuntu

@AlanT1337 said:

I think it was build in my normal Qt folder

I suppose that's possible, if you're using the qmake from that location to run on the project file. In any case I'm glad it's working now.

@tomasz3dk Wielkie dzięki, pomogło :)

@stackprogramer said:

@JohanSolo
i now defined its works now thanks for reply.

I'm glad I could help, Please don't forget to mark the question as solved.

@kshegunov Thank you so much for the help! Such a simple mistake