Why Does My Qt 5 Static Build Crash on Windows with an Access Violation Error?

Deploying Qt 5 App on Windows: Troubleshooting Access Violation Errors

Deploying Qt 5 applications on Windows can be challenging, especially when using static builds. This article explores an experienced issue where a Qt 5 static build crashed on "clean" PCs without a clear error message in Windows 8.

Troubleshooting Steps:

To resolve the access violation error, the following steps were taken:

1. Using Dependency Walker: Running Dependency Walker (depends.exe) on Windows 7 revealed an access violation originating from QtGui.dll. The error message indicated:

   Second chance exception 0xC0000005 (Access Violation) occurred in "QT5GUI.DLL" at address 0x61C2C000.

2. Introducing windeployqt: Starting from Qt 5.2, the windeployqt tool simplifies application deployment. This tool automatically copies necessary Qt dependencies alongside the .exe file.
3. Specifying QML Directory: To include QML dependencies, use the --qmldir option when running windeployqt. This informs the tool about the location of QML files.
4. Testing on Clean System: Ensure that all required files are included by testing the application on a computer without Qt SDK installed, or temporarily rename the Qt directory. This prevents the application from referencing missing files from the SDK.

Conclusion:

By following these steps, the access violation error in the Windows 8 static build was resolved, allowing the Qt 5 application to deploy successfully on "clean" systems.

The above is the detailed content of Why Does My Qt 5 Static Build Crash on Windows with an Access Violation Error?. For more information, please follow other related articles on the PHP Chinese website!