LNK1181: the input file cannot be opened "release\CameraImageWrapper.obj"
-
Re: UINT32_C' & 'UINT64_C': identifier not found error in Qt6.3.0 MSVC2019 64-bit
I managed to fix the problem using the advice of @c-toyama. But after that I got a build error.
LNK1181: the input file cannot be opened "release\Camera Image Wrapper.obj"What could be the matter? Thank u
-
X xlartas marked this topic as a regular topic on
-
X xlartas marked this topic as a question on
-
X xlartas marked this topic as a regular topic on
-
X xlartas marked this topic as a question on
-
Re: UINT32_C' & 'UINT64_C': identifier not found error in Qt6.3.0 MSVC2019 64-bit
I managed to fix the problem using the advice of @c-toyama. But after that I got a build error.
LNK1181: the input file cannot be opened "release\Camera Image Wrapper.obj"What could be the matter? Thank u
@xlartas said in LNK1181: the input file cannot be opened "release\CameraImageWrapper.obj":
LNK1181: the input file cannot be opened "release\Camera Image Wrapper.obj"
What could be the matter? Thank uThe file does not exist.
The file does exist but the spaces in the file name are a problem. -
@xlartas said in LNK1181: the input file cannot be opened "release\CameraImageWrapper.obj":
LNK1181: the input file cannot be opened "release\Camera Image Wrapper.obj"
What could be the matter? Thank uThe file does not exist.
The file does exist but the spaces in the file name are a problem.@ChrisW67 There are no spaces in the console, I do not know why it was copied like that. In the folder with the build, only ".i" files are generated, there is no .obj, apparently the error occurs before they are created. But if I disable QZXing.pri, everything builds well.
-
@ChrisW67 There are no spaces in the console, I do not know why it was copied like that. In the folder with the build, only ".i" files are generated, there is no .obj, apparently the error occurs before they are created. But if I disable QZXing.pri, everything builds well.
-
@xlartas So you have not removed the temporary
QMAKE_CXXFLAGS += -Pmade to debug the problem in the post you linked. The /P option suppresses compilation. It does not produce an .obj file.... -
@ChrisW67 Its's my .pro
QT += core gui widgets concurrent network greaterThan(QT_MAJOR_VERSION, 4): QT += widgets CONFIG += c++17 include(QZXing/QZXing.pri) QMAKE_CXXFLAGS += -P SOURCES += \ main.cpp \ scanner.cpp HEADERS += \ scanner.h FORMS += \ scanner.ui qnx: target.path = /tmp/$${TARGET}/bin else: unix:!android: target.path = /opt/$${TARGET}/bin !isEmpty(target.path): INSTALLS += target -
@ChrisW67 Its's my .pro
QT += core gui widgets concurrent network greaterThan(QT_MAJOR_VERSION, 4): QT += widgets CONFIG += c++17 include(QZXing/QZXing.pri) QMAKE_CXXFLAGS += -P SOURCES += \ main.cpp \ scanner.cpp HEADERS += \ scanner.h FORMS += \ scanner.ui qnx: target.path = /tmp/$${TARGET}/bin else: unix:!android: target.path = /opt/$${TARGET}/bin !isEmpty(target.path): INSTALLS += target@xlartas I have solved the problem. Just don't use QZXing with 6.3.2MSVC Static build qmake. Use a regular zxing-cpp built using the visual studio dev console.
cmake -S zxing-cpp -B zxing-cpp.release -DCMAKE_BUILD_TYPE=Release -DBUILD_SHARED_LIBS=OFF -DCMAKE_MSVC_RUNTIME_LIBRARY=MultiThreaded -DCMAKE_CXX_STANDARD=17 -A x64zxing-cpp.release -> rename -> zxing | and move to project folderConnect the library to the .pro file
win32: LIBS += -L$$PWD/zxing/core/Release/ -lZXing INCLUDEPATH += G:/zxing-cpp/core/src DEPENDPATH += G:/zxing-cpp/core/src win32:!win32-g++: PRE_TARGETDEPS += $$PWD/zxing/core/Release/ZXing.lib else:win32-g++: PRE_TARGETDEPS += $$PWD/zxing/core/Release/libZXing.aMake an include. Please note that the order of imports is sometimes important.
#include "ReadBarcode.h" #include <ImageView.h> #include <BarcodeFormat.h> ... and others if you need -
X xlartas has marked this topic as solved on