Installation and Deployment

@jsulm It has no business with g++. g++ is installed, and even though not, I have clang++ still.

Got it! I installed the "Dependency Walker" [1] application to inspect my binaries, starting by my .exe file. No reference to Qt5Cored.dll, but when I opened the quazip.dll file, it is listed! I recompiled Quazip, using this qmake line: qmake -config release "LIBS+=C:\extralibs\zlib1.dll" "PREFIX=C:\Quazip" And now, the problem is solved! Thank your for the dependencies hint! :) [1] : http://www.dependencywalker.com/

@SGaist Hi, friend) I search freeware soft)

@collycrk Sorry for the quick draw. While I was waiting for an answer to this error I, in release mode, ran a clean all and then ran build project. And everything worked as expected. This post is solved.

@jsulm wow, thanks dude. thought its a other problem. anyways same package for linux mint ;)

I could finally find that the cause of the issue are the 'platforminputcontexts' plugins. It seems that the even if my application didn't contain them, the precompiled Qt libraries could load and use some system plugins.

Hmm, It did seem to come out that way , even tho I did it backwards so I could include the SDK .

Because there are some additional information to link the library to its corresponding debugging symbol. You have here A pretty interesting article on the subject.

Hi, What do you mean by "nothing happens` Don't you have any error message ?

@amigo421 hi i know 100% between mingw and VS is a no go, but also seen that sometimes versions of VS also is no good.

i still think there is simpler explanation for your issue. The linker can't even find the lib file specified. Are you really sure that the libs are in "C:\source\icu2\lib"? And not in a release/debug subfolder, etc.?

@jsulm i did not do anything on the android device

Hi, The basics can be found here Don't forget the licensing implication of a static build.

@Bart_Vandewoestyne said: we're storing our Qt build in our version management system This is a strange thing to do, since Qt guarantees binary compatibility between minor versions, but well, you're free to choose. Unfortunately, I don't see how you could decrease the size further, beside deleting the docs, as the libraries are in the /lib directory and they're the next biggest size. Maybe store only the libs that you're using, i.e. these that you're going to deploy. No point in keeping QtXml if you're not using it, right?

Have now refined Avast to just stop checking executables and all still OK. I have not seen any mention of the possible clash with anti-virus software in any of the places I hunted for solutions. I think it should go in a FAQ somewhere. It would have saved me hours of frustration. Such a simple solution that I would never have thought of.

@Krag Hi Maybe just uninstall and install to c:\qt if possible Im not 100 sure its the issues but looking at the screenshot, it seems like. If you move it by hand, im not sure all paths match up. But you can try and see if it still works :)