Unknown module(s) in QT: quick qml

Xooch · wrote on 9 Jun 2014, 13:20

In my situation I did build from the root folder, and performed the build out-of-tree. I created a directory, and called configure from that directory, did the make and make install.

It does turn out to be an installation problem - the libraries were actually built. For example, I found ./qtdeclarative/lib/libQt5Qml.so in my build tree.

When I go to Options | Build & Run, on the Qt Versions tab, I've added the qmake that is in my build directory, but there is a warning "Non-installed -prefix build - for internal development only." What is this warning?

Also, when during the build is it trying to find the quick and QML libraries? It's not looking on the target as far as I can tell, so what is telling Creator that these libraries exist (or don't)?

sierdzio · wrote on 9 Jun 2014, 13:36

Out-of-source prefixed builds are not working very well when cross-compiling. I recommend doing in-source builds when compiling for ARM and Android.

Xooch · wrote on 9 Jun 2014, 18:00

Ok, so I reconfigured and re-built using a fresh source tree, and I configured, make, make install from that source tree. This time I'm pretty sure I got everything installed properly: I added the -extprefix option to configure, which appears to be the real cause of the missing libraries.

However, I'm still having the same problem from Creator. The quick and qml libraries are definitely on my target. I've updated my kit to point to the appropriate things, but I still get "unknown module(s) in QT: quick qml", and I still get the yellow "!" on the Qt Versions tab when setting up the kit, with the message "non-installed -prefix build - for internal development only".

Any further suggestions? It seems like the "non-installed -prefix build" is probably the error I need fixed next, I believe.

For the record, here is my new configure command line:

@./configure -debug -opengl es2 -device linux-am335x-g++ -device-option CROSS_COMPILE=/home/steve/ti-sdk-am335x-evm-07.00.00.00/linux-devkit/sysroots/i686-arago-linux/usr/bin/arm-linux-gnueabihf- -sysroot /home/steve/ti-sdk-am335x-evm-07.00.00.00/linux-devkit/sysroots/cortexa8hf-vfp-neon-3.8-oe-linux-gnueabi -prefix /home/steve/ti-sdk-am335x-evm-07.00.00.00/targetNFS -extprefix /home/steve/ti-sdk-am335x-evm-07.00.00.00/targetNFS -no-glib -qpa eglfs -opensource -confirm-license@

sierdzio · wrote on 9 Jun 2014, 18:02

Please pay close attention what the configure says when it's finishing: maybe you should not be running "make install" at all.

Xooch · wrote on 9 Jun 2014, 18:26

I have to, though - somehow the necessary files need to get into my target filesystem. I did re-run configure to find the message you're talking about (I've seen it, but I can't remember the details), but that message did not appear. Also, I don't think I fit into the category of "must not run make install".

Here are the messages printed at the end of configure:

NOTE: Qt is using double for qreal on this system. This is binary incompatible against Qt 5.1.
Configure with '-qreal float' to create a build that is binary compatible with 5.1.

Qt is now configured for building. Just run 'make'.
Once everything is built, you must run 'make install'.
Qt will be installed into /home/steve/ti-sdk-am335x-evm-07.00.00.00/targetNFS

sierdzio · wrote on 9 Jun 2014, 18:32

Yeah, you are right. Weird :)

Xooch · wrote on 9 Jun 2014, 18:34

Perhaps this might shed some light? I'm not sure though...

When setting up the Qt Version in the Options dialog, the paths for Qt are displayed like the image below. It appears most of these paths points to spots in the Qt source tree, not to where the actual installation is.

My installation should go to /home/steve/ti-sdk-am335x-evm-07.00.00.00/targetNFS, which is the directory I'm exporting via NFS.

!http://i.imgur.com/wvwpHjw.png(Qt kit details)!

Xooch · wrote on 9 Jun 2014, 21:09

I just reconfigured and re-built (with a fresh source tree), removing the -prefix option (thinking it might be conflicting with -extprefix), but no luck. AAARGH!

Xooch · wrote on 10 Jun 2014, 20:10

As it turns out, I needed to point Creator to the qmake of the target, not to qtbase/bin/qmake in my build tree.

Which them leads to a new question: How does Creator make use of a binary built for a different architecture?!? It’s definately not running “qmake -query QT_SOME_VAR” on my embedded device!

bootchk · wrote on 17 Oct 2014, 13:15

Please, what exactly did you do to 'point Creator to the qmake of the target'?

I think Creator is running /usr/bin/qmake, which is not the qmake from the android kit. I suppose I could use a link, but is there another way?

I think Creator uses qmake not only to generate a makefile, but to query locations in the kit. So if it uses /usr/bin/qmake, it doesn't find the quick module (which is not installed on the original Ubuntu installation of Qt 5.2.1) But if it uses ~/Qt/5.3/android/bin/qmake, it would find the quick module.

W. Fiderek · wrote on 2 Sept 2015, 08:56

Had same issue on lubuntu and Qt 5.2.1.
I removed Qt configuration files from .config folder in my home dir.
rm -r ~.config/QtProject
rm ~.config/QtProject.conf

Reconfigure project again and all works as expected