QML_IMPORT_NAME seems to be an unknown variable, qml module not found

Question

I'm trying to run this example with qt 5.15.1

When I declare QML_IMPORT_NAME, the variable seems to be unknown from qt (see the font's color on the below screenshot) and when I import "com.mycompany.messaging" in my qml file, I have an error "QML module not found."

Edit: After some investigations, the code runs as it should but I have this error in Qt Creator. If I want to edit qml file with the gui editor, I need to comment out all code related to the backend in text mode before otherwise, it fails to open the file.

What is the trick?

Did you add the QML_ELEMENT (or similar) macro to a C++ type? — Mitch
– Mitch, Commented Sep 28, 2020 at 10:37
Yes. : class UiBackend : public QObject { Q_OBJECT Q_PROPERTY(QString userName READ userName WRITE setUserName NOTIFY userNameChanged) QML_ELEMENT public: — Julien
– Julien, Commented Sep 28, 2020 at 11:12
The example works for me. You said you're using "qt 15.1", which I assume is a typo and that you're actually using 5.15.1? Did you run qmake and rebuild after making the changes? — Mitch
– Mitch, Commented Sep 28, 2020 at 12:46
Yes, right 5.15.1, I did qmake and rebuild many times.... :( — Julien
– Julien, Commented Sep 28, 2020 at 15:56
Can you tell me if QML_IMPORT_CONFIG is coloured in your pro file ? — Julien
– Julien, Commented Sep 28, 2020 at 15:59

Julien · Accepted Answer · 2020-10-02 09:10:24Z

1

With this, I assumed I should have added

CONFIG += qmltypes

to .pro file. But since, I switched to cmake and did not find an equivalent, so I used the old method with:

qmlRegisterType<Person>("People", 1,0, "Person");

in main.cpp (see above link).

answered Oct 2, 2020 at 9:10

Julien

8901 gold badge9 silver badges21 bronze badges

Sign up to request clarification or add additional context in comments.

Comments

luffy · Accepted Answer · 2021-08-13 12:05:36Z

1

This is a known bug that is not fixed yet (https://bugreports.qt.io/browse/QTCREATORBUG-24987).

The reason for the error is that QtCreator requires the generated .qmltypes and metatypes.json files next to the application binary.

A workaround for this is to add the following to your pro file:

CONFIG(debug, debug|release) { 
    EXE_DIR = $${OUT_PWD}/debug
} else { 
    EXE_DIR = $${OUT_PWD}/release
} 

CONFIG += file_copies 
COPIES += qmltypes metatypes 

qmltypes.files = $$files($${OUT_PWD}/$${TARGET}.qmltypes)
qmltypes.path = $${EXE_DIR} 

metatypes.files = $$files($${OUT_PWD}/$${TARGET}_metatypes.json)
metatypes.path = $${EXE_DIR}

answered Aug 13, 2021 at 12:05

luffy

2,4283 gold badges27 silver badges30 bronze badges

Collectives™ on Stack Overflow

QML_IMPORT_NAME seems to be an unknown variable, qml module not found

2 Answers 2

Comments

Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related