QT Creator编译程序启动报错0x00007b及消除DLL依赖咨询

Hey there, let's break down your problem step by step—this is super common with Qt apps, so we'll get you sorted out.

一、先搞定"应用程序无法启动(0x00007b)"错误 #

This error almost never boils down to just missing DLLs—it’s usually a mismatched architecture (e.g., you built a 64-bit app but copied 32-bit DLLs, or vice versa) or wrong version of VC++ runtime libraries. Here’s how to fix it:

• First, confirm your build architecture matches your system: If you’re on 64-bit Windows, check that your Qt Creator Kit is set to Desktop Qt X.X.X MSVC20XX 64bit (not the 32-bit variant).
• Skip manual DLL hunting—use Qt’s built-in tool to auto-copy the right files: Open Qt Creator’s terminal (or a system cmd, first navigate to your Qt bin folder like C:\Qt\X.X.X\msvc20XX_64\bin), then run:

  windeployqt.exe "path/to/your/app.exe"
  

  This tool automatically detects and copies all required Qt DLLs, VC++ runtime files, and even critical plugins (like the qwindows.dll platform plugin—this is the #1 thing people miss when manually copying DLLs) to your exe’s folder.

二、Why manual DLL copying fails #

When you add DLLs by hand, you’re likely hitting one of these issues:

• Wrong version: Qt DLLs must match your exact Qt build version (e.g., Qt 5.15.2 DLLs won’t work with a 5.14-built app).
• Missing plugins: Platform or utility plugins are required for the app to launch, and they’re easy to overlook when copying files manually.
• Architecture mismatch: 64-bit apps can’t load 32-bit DLLs, and vice versa—this is the most common cause of the 0x00007b error.

三、How to eliminate DLL dependencies entirely #

To make your exe run on any Windows PC without extra files, you need to statically compile Qt, which bundles all Qt libraries and dependencies directly into the exe. Here’s how:

1. Download Qt source code: Use the Qt Installer to select the "Source" component for your Qt version, or grab the source package from the Qt website.
2. Set up the static build environment:
   • Open the VS Command Prompt matching your compiler (e.g., x64 Native Tools Command Prompt for VS 20XX—must align with your Qt compiler version).
   • Navigate to the Qt source root folder, then run the configure command:

     configure -static -release -prefix "C:\Qt\Static\X.X.X" -opensource -confirm-license -no-opengl -skip qtwebengine
     

     Quick breakdown of key flags:
     • -static: Enables static compilation
     • -release: Builds a release (not debug) version
     • -prefix: Sets the install path for your static Qt build
     • -no-opengl/-skip qtwebengine: Optional, speeds up compilation by skipping components you don’t need
3. Compile and install static Qt:
   Run these commands (this will take a while—grab a coffee):

   nmake
   nmake install
   

4. Add a static Kit to Qt Creator:
   Go to Tools > Options > Kits, create a new Kit, select your matching MSVC compiler, and point the Qt version to your newly installed static Qt folder.
5. Build your app with the static Kit:
   Select the static Kit, compile a Release version, and the resulting exe will be fully standalone—no DLLs needed to run on other PCs.

Quick extra notes #

• If you’re using third-party libraries (like OpenCV or SQLite), you’ll need to statically compile those too, otherwise you’ll still have DLL dependencies.
• Statically compiled exes are significantly larger than dynamically built ones—that’s normal, since all dependencies are packed into a single file.

内容的提问来源于stack exchange，提问作者Chadi To