Qt3DExtras: No such file or directory
-
Hello guys)
Problem:
I can’t connect Qt3DExtras, although when I connect this module in the .pro file it doesn’t give an error. Examples do not work either.
What was done:
I installed qt3d5-dev and qt3d5-dev-tools. This did not give effect.
Then I installed everything related to qt3d, with the command:
"sudo apt install qt3d *"
Nothing has changed either.
System:
Description: Ubuntu 19.10
Release: 19.10
Codename: eoan
qtCreator: 4.8.2
Qt 5: 5.12.4
Please help me I have no ideas. -
Hi and welcome to devnet,
What does your .pro file contain ?
-
I do not think this problem is related to this, since the examples (simple-cpp and basicshapes-cpp) give the same error. This is *.pro file:
QT += 3dcore 3dlogic 3dextras 3dinput greaterThan(QT_MAJOR_VERSION, 4): QT += widgets CONFIG += c++11 DEFINES += QT_DEPRECATED_WARNINGS SOURCES += \ main.cpp HEADERS += qnx: target.path = /tmp/$${TARGET}/bin else: unix:!android: target.path = /opt/$${TARGET}/bin !isEmpty(target.path): INSTALLS += target -
What exact error do you get ?
-
I do not think this problem is related to this, since the examples (simple-cpp and basicshapes-cpp) give the same error. This is *.pro file:
QT += 3dcore 3dlogic 3dextras 3dinput greaterThan(QT_MAJOR_VERSION, 4): QT += widgets CONFIG += c++11 DEFINES += QT_DEPRECATED_WARNINGS SOURCES += \ main.cpp HEADERS += qnx: target.path = /tmp/$${TARGET}/bin else: unix:!android: target.path = /opt/$${TARGET}/bin !isEmpty(target.path): INSTALLS += target@vitaliy2034 said in Qt3DExtras: No such file or directory:
SOURCES +=
main.cppIs it an editor error? There should be as backslash, like this:
SOURCES += \ main.cppIt is an old maxim of mine that when you have excluded the impossible, whatever remains, however improbable, must be the truth. (Sherlock Holmes)
-
@vitaliy2034 said in Qt3DExtras: No such file or directory:
SOURCES +=
main.cppIs it an editor error? There should be as backslash, like this:
SOURCES += \ main.cpp@KroMignon Missing coding quotes but still, the HEADERS seems to be empty.
-
I have found solution!!! After reinstalling system all work fine. To my mind It was the HDD problem.
