1. Add library files to the project
Open the VS solution, find your project, right-click Properties, and you'll see as shown in
(2). Locate the corresponding DLL file in the QT Bin directory
Note that with D for debug edition. For example, QtsqlD4.lib Here is the debug version of the meaning, the release is released version, so to find the corresponding release version, is no D version.
Also add the Windows library file.
Debug
C:\Program Files\Microsoft Visual Studio 8\vc\redist\debug_nonredist\x86\microsoft.vc80.debugcrt
Release
C:\Program Files\Microsoft Visual Studio 8\vc\redist\x86\microsoft.vc80.debugcrt
If you are debugging debug, just copy the files in the debug directory. If it is release, copy the files in the release directory.
(3). This is the normal software release. In general, there is no problem.
But I found that after this process was packaged, a run on another machine crashed.
So the pain of the commissioning began, debugging found after the problem is because of coding. I used GBK encoding, and did not put the code on the library if, so led to a run on the hang. Note that Utf-8 is cross-platform, so library files are not required. Well know the reason, is to add the encoded library file.
Find the QT installation directory, D:\win_software\qt-everywhere-opensource-src-4.7.3\plugins\codecs (this is my installation directory), in addition to the debug version of the DLL, the others are to be copied. and also to re-establish a directory called codecs, but also to add the Windows library file, is the above debug or release path files.
This is the package directory for the project file
This is the code library file packaging directory
QT software release on other machines cannot run (IDE for VS2005)