@hem1 ok regarding -make libs, but what about this:
device: you -> linux-rpi3-g++ guide -> linux-rasp-pi3-g++
did you try that different device naming?
actually the device name depends on the folder name present in qtbase of QT folder which was like linux-rpi3-g++ so i used that otherwise it was giving error no device named linux-rasp-pi3-g++ present.
thank you very much for your suggestion. I've done a second Qthread for calculation. so the cycle is the following.
Read cam_image with one thread every QTimer event (200ms). I've inserted a QThread::msleep(100) in the first thread, for letting the second thread to work, as you suggested.
Pass the the Mat data to the second thread for calculating ORB algorithm
Pass back the Mat, where the algorithm has been applied, to the first thread.
Convert Mat file to image and pass the QIMage to GUI thread.
The frame rate got an increasement up to 9 FPS (which is much more than before!).
For passing Mat object among threads, I had to register Mat type as follow:
Hello to all,
as far as I can understand, for those people which are using Yocto and want to use QtVirtualKeyboard, they have to install Boot2Qt, which contains recipes for installing the required software and making custom images.
See below: http://doc.qt.io/QtForDeviceCreation/qtee-about-b2qt.html
There's another solution worth investigating. Since your images are likely not going to change size, you could make m_image directly the right size and then wrap the data from it in the dest Mat (see this constructor). Doing so you you can remove the m_image = etc. line.
thank you again for your answer. I didn't know of this library, and it looks simpler to use than the qt wrappeer that I found, I'll definitely pass to this.
Just for information for those ones who use Yocto, the problem was that I had to add the following for seeing modbus.h:
INCLUDEPATH += $$PWD/../../../../opt/poky/sdk-2.2.2/sysroots/cortexa7hf-neon-vfpv4-poky-linux-gnueabi/usr/include/modbus
DEPENDPATH += $$PWD/../../../../opt/poky/sdk-2.2.2/sysroots/cortexa7hf-neon-vfpv4-poky-linux-gnueabi/usr/include/modbus
After that I had the following problem:
cannot find /lib/arm-linux-gnueabihf/libpthread.so.0
and found solution here: https://stackoverflow.com/questions/14207189/crosstools-ng-cant-find-pthread-so
@SGaist Hello SGaist,
thank you very much for your answer. I've build an OS image and sdk with yocto poky-morty so that I could cross compile my applications for a Raspberrypi3.
Qt version is 5.7.1.
I feel a little silly but I found out what was wrong.
Basically my touch was rotated of 180 compare to my screen. So when I pressed on QDial, which is in the middle of the screen, it worked while when I pressed a button on the corner the clicked() release() could not be launched. Thank you anyway.
P.S. I've got another problem with libmodus, opened in another thread, could you look at it :) ?
what do you want to do exactly?
The QtAutomotive QML module is only available for commercial licenses.
Do you want to access the car's CAN bus? Then you can use the QtSerialBus module (see this CAN example)
that's because you have to re sync everything with the new version of Qt on your raspberry pi. also you have to run the phyton script to fix the symbolic links again and then to do the rsync.. also if you are using the rpi.. then you have to take everything from them. the image the qt5pi folder and so on...
Also please note that their files are based on this tutorial found on Qt website http://wiki.qt.io/RaspberryPi2EGLFS