Qt+OpenCV开发摄像头显示控件遭遇LNK1107: invalid or corrupt file cannot read 0x458错误求助

Hey there! I’ve dealt with this exact linker error a few times when mixing Qt and OpenCV, so let’s break down what’s going wrong and how to fix it. This error almost always boils down to mismatched library types, conflicting compiler configurations, or corrupted/incorrectly linked files in your .pro file.

Key Issues in Your Current Setup #

First, let’s spot the red flags in your .pro file:

• You’re directly linking DLL files in the LIBS section—linkers only need .lib import libraries, not .dll files (those are for runtime execution).
• You’ve mixed MSVC (vc15) and MinGW library paths, which will cause conflicts if your Qt Kit uses only one of those compilers.
• There’s duplicate INCLUDEPATH and LIBS entries that are cluttering the build configuration.

Step-by-Step Solutions #

1. Clean Up the .pro File #

Here’s a fixed version of your .pro file—remove all the problematic lines and use this instead. I’ll explain the changes below:

#-------------------------------------------------
#
# Project created by QtCreator 2019-08-10T12:27:53
#
#-------------------------------------------------
QT += core gui
greaterThan(QT_MAJOR_VERSION, 4): QT += widgets

TARGET = TutorialOpenCV
TEMPLATE = app

DEFINES += QT_DEPRECATED_WARNINGS
CONFIG += c++11

SOURCES += \
        main.cpp \
        mainwindow.cpp \
        myvideocapture.cpp

HEADERS += \
        mainwindow.h \
        myvideocapture.h

FORMS += \
        mainwindow.ui

# Default rules for deployment.
qnx: target.path = /tmp/$${TARGET}/bin
else: unix:!android: target.path = /opt/$${TARGET}/bin
!isEmpty(target.path): INSTALLS += target

# OpenCV Configuration (MSVC 2017 x64)
# Adjust the paths to match your actual OpenCV install location
OPENCV_PATH = C:/opencv/build
OPENCV_LIB_PATH = $$OPENCV_PATH/x64/vc15/lib

INCLUDEPATH += $$OPENCV_PATH/include
DEPENDPATH += $$OPENCV_PATH/include

# Link release/debug libraries separately
win32:CONFIG(release, debug|release): LIBS += -L$$OPENCV_LIB_PATH -lopencv_world451
else:win32:CONFIG(debug, debug|release): LIBS += -L$$OPENCV_LIB_PATH -lopencv_world451d

Changes Made:

• Removed all direct .dll links from LIBS—we only link the .lib import libraries here.
• Removed duplicate and conflicting INCLUDEPATH entries (only keep the base OpenCV include path).
• Removed MinGW-specific paths—if you’re using a MinGW Qt Kit, you’ll need to download/build OpenCV with MinGW instead of MSVC vc15.
• Used variables for paths to make the file cleaner and easier to adjust.

2. Match Compiler Architecture #

Your OpenCV build is for x64 (x64/vc15), so your Qt project must use an x64 compiler kit:

1. In Qt Creator, go to Projects > Build & Run.
2. Under Kit, select a kit that uses an x64 compiler (e.g., "Desktop Qt 5.12.8 MSVC2017 64bit").
3. If you don’t have an x64 kit installed, you’ll need to add it via the Qt Maintenance Tool.

3. Verify OpenCV Library Files #

The 0x458 error can also happen if your .lib files are corrupted:

• Try re-downloading OpenCV (make sure to get the correct version for your compiler/architecture).
• If you built OpenCV from source, recompile it to generate fresh .lib files.

4. Clean and Rebuild the Project #

Old build cache can cause weird linker issues:

1. Go to Build > Clean All to delete intermediate files.
2. Delete the build-TutorialOpenCV-* folder in your project directory.
3. Rebuild the project with Build > Rebuild All.

5. Set Up Runtime DLLs #

Once the project links successfully, you’ll need to make sure the OpenCV DLLs are available at runtime:

• For Release mode: Copy opencv_world451.dll from C:/opencv/build/x64/vc15/bin to your project’s release output folder.
• For Debug mode: Copy opencv_world451d.dll to your project’s debug output folder.
• Alternatively, add C:/opencv/build/x64/vc15/bin to your system’s PATH environment variable.

Quick Check for Your Code #

Your MyVideoCapture and MainWindow code looks okay, but one small improvement: in the MainWindow destructor, call quit() before terminate() to properly stop the thread (avoiding resource leaks):

MainWindow::~MainWindow()
{
    delete ui;
    mOpenCV_videoCapture->quit();
    mOpenCV_videoCapture->wait(); // Wait for the thread to finish safely
    delete mOpenCV_videoCapture; // Don't forget to delete the object!
}

Using terminate() can leave resources hanging, so it’s better to quit gracefully.

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