App becoming white when running on Windows without Qt installed

[Momergil]

Thanks d_stranz for the reply.

The answer is "Yes" for all of your items.

Any other tip?

[d_stranz]

OK, what other external things might your program depend on? Windows runtime libraries present on your Qt systems but not your non-Qt systems? Images? QML files? If the programs run up without complaints about missing DLLs, then it implies that there is some other dependency you aren't satisfying.

I would suggest trying to get a very simple,"Hello World" QDialog-based app to run. If that works, then it probably isn't a Qt problem.

[Momergil]

Thanks again for the reply, d_stranz.

I would suggest trying to get a very simple,"Hello World" QDialog-based app to run. If that works, then it probably isn't a Qt problem.

I'm asking myself why I didn't think about that earlier... Either way I tried it and the problem appeared again - it was a QMainWindow with a QLabel installed in the same folder where the real app resides with the same pack of libs, images and etc. around. So I suppose this makes us go back to the DLLS - or to a relation between those and the 2 PCs¹ such as a particular graphics driver and so forth.

Either way thanks. Any other suggestion in mind?

¹: although I tested the Hello World app in only one of them, which I suppose it's enough for that test.

[d_stranz]

Any other suggestion in mind?

No idea. I'd still suggest a completely independent install of a QDialog-based Hello World app is a fresh directory. If there is a problem with one of the DLLs you have installed with your other app, then running a different EXE from the same directory isn't going to help much with diagnosing the problem.

[Momergil]

No idea. I'd still suggest a completely independent install of a QDialog-based Hello World app is a fresh directory. If there is a problem with one of the DLLs you have installed with your other app, then running a different EXE from the same directory isn't going to help much with diagnosing the problem.

Hi d_stranz once again!

Well I accepted your last suggestion and did exactly that in one of the buggy machines. This was some days ago so I can't remember for certainty, but if I'm not mistaken everything worked fine then. I then decided to put my app inside its place and, guess what, everything worked fine.

Then I decided to test again (the whole process) in the second machine and the problem appeared again. Funny fact was that when I executed my test app inside a remote repository (with the DLLs there), things got right, but running the exact same app and libs inside a folder located inside the machine, the bug appeared. It didn't take much time, though, for the PC owner report that that could truly be a machine problem since he just found that another app, not developed with Qt, was having the exact same problem.

So, for the time being, I've concluded that the bug was solved (although I'm still not sure why and how).

Thanks for all the help!