Some of the QT programs encountered porting issues between Windows platforms are collated

Today, we try to transplant the QT program into various virtual machines, because Qt's dependent library reports often fail to show all dependent libraries. The result frequently appeared the problem, finally all solved, here gives some routines.

First of all for the QT version, I used a lot, the end of the current recommended MINGGW version (this version comes with MINGGW), the website link:

Qt 5.4.2 for Windows 32-bit (MinGW 4.9.1, 852 MB) (info)

My personal Baidu network disk Link: Qt 5.4.2 MinGW

The installation should be careful to check the MinGW, if you do not. This version can be run under windowsxp.

Then I'll introduce a tool: Process Explorer v16.01 This tool to see the dependent libraries. First time use to set up a bit first

You will then be able to find the dependent files for each of your running programs on the left.

Examples of specific operations:

I want to port my QT program (myexe) to Windows XP, then I install QT on the Windows XP virtual machine/machine, then copy the code into the release version, and then use the Process Explorer to see the libraries that they depend on after the compilation is successful. Copy them all to the same directory as the compiled program to run successfully.

(In the end, it's more hassle than Linux ...) For Linux, you can use LDD to view dependent libraries)

Some of the QT programs encountered porting issues between Windows platforms are collated