Installing new module

SGaist · wrote on 25 Sept 2019, 11:51

Hi,

Mostly the same you would if building Qt for your desktop:

Get the module sources
Use the qmake executable of your cross-compiled Qt version
Call make && make install

Pablo J. Rogina · 26 Sept 2019, 14:39

@vishbynature said in Installing new module:

steps to install new modules

You may want to check this guide, especially step 16.

vishbynature · 26 Sept 2019, 14:55

@Pablo-J-Rogina , @SGaist
I have not installed Qt on this UBuntu, I got it done from someone else and for now I dont have that help. I had read the RaspberryPi2EGLFS doc step 16
but couldnt make anything out of it. Now searching for a Simpler explanation.

Pablo J. Rogina · 30 Sept 2019, 09:18

@vishbynature

Now searching for a Simpler explanation

"Everything should be as simple as it can be but not simpler" Albert Einstein.

vishbynature · 10 Jul 2019, 10:33

@Pablo-J-Rogina @SGaist
ohk.
I was able to make the serialport module. qtserialport folder was inside the build folder of Qt and then I followed the step 16 from documentation, it worked.
Now I want to install the "bluetooth" module. No folder called qtbluetooth inside build folder. From where on Internet should I download this folder?

SGaist · 30 Sept 2019, 13:45

Bluetooth support comes from the QtConnectivity module.

vishbynature · S SGaist 30 Sept 2019, 09:19

@SGaist,
ok, I will make QtConnectivity module.

vishbynature · 10 Jan 2019, 12:46

@SGaist
I was able to make the module and run my program in raspberry pi
but for now I have this message:
qt.bluetooth: Dummy backend running. Qt Bluetooth module is non-functional. on both my RPi and ubuntu 16.04.
I followed this thread.
working on it.
update:
my ubuntu 16.04 Qt program is able to communicate with raspberry pi python program. I have error in raspberry pi only now.

qt.bluetooth: Dummy backend running. Qt Bluetooth module is non-functional.

vishbynature · wrote on 1 Oct 2019, 13:01

@SGaist @Pablo-J-Rogina
I found this post suggesting you have to install libraries in between steps 6 and 8 while making raspberry pi. Is this link relevant?

SGaist · 2 Oct 2019, 06:49

Yes it is.

You need to have the development packages of the needed dependencies for your target available in the sysroot you use to cross-compile Qt.

vishbynature · 10 Feb 2019, 06:59

@SGaist
ok I followed the procedure , installed All the libraries as mentioned in the link after step 6 and step 8 and made new raspberry pi, still i get the same Error message on RPi. I installed stretch lite on my RPi does this have any bearing? or there is something more to be done?
Does my Qt creator in ubuntu needs to be made again?

SGaist · 3 Oct 2019, 07:02

Might be a silly question but did you update the sysroot on your desktop machine ?

If so, did you rebuild the Qt Connectivity module from scratch ?

vishbynature · 3 Oct 2019, 14:38

@SGaist
about sysroot no I did not update it, i just follow plain steps to make RPi only.
my sysroot has folder of bluetooth in /usr/include directory.
and about Qt Connectivity yes I did make this module from scratch.
may be after making Qtconnectivity bluetooth folder was created in sysroot.

Pablo J. Rogina · 3 Oct 2019, 19:30

@vishbynature said in Installing new module:

about sysroot no I did not update it, i just follow plain steps to make RPi only.

Please check step #8:
Using rsync we can properly keep things synchronized in the future as well

so whenever you install libraries/headers in your device, you need to keep it in sync in the sysroot folder in your host

vishbynature · wrote on 3 Oct 2019, 19:30

@Pablo-J-Rogina
ok for start
you need to keep it in sync in the sysroot folder in your host.
how is this achieved?
what i follow is I make creator and Rpi and for another RPi i will follow the procedure of its make. Now if in between we want to install and add new feaures like use of Qbluetooth i will make Qtconnectivity. now what sould I do to keep sysroot in sync?
and what to do to make this work on my RPi?

SGaist · 4 Oct 2019, 08:32

@Pablo-J-Rogina already provided the answer in italic: rsync.

vishbynature · 5 Oct 2019, 11:59

@SGaist @Pablo-J-Rogina
I am following the steps properly
which include:
rsync -avz pi@raspberrypi.local:/lib sysroot
rsync -avz pi@raspberrypi.local:/usr/include sysroot/usr
rsync -avz pi@raspberrypi.local:/usr/lib sysroot/usr
rsync -avz pi@raspberrypi.local:/opt/vc sysroot/opt
of step 8.

vishbynature · wrote on 5 Oct 2019, 11:59

I have installed these libraries on Rpi before rsync steps
libqt5bluetooth5 and qtconnectivity5-dev
libbluetooth-dev bluetooth blueman bluez libusb-dev libdbus-1-dev bluez-hcidump bluez-tools python-bluez.
@Pablo-J-Rogina @SGaist .

SGaist · 7 Oct 2019, 05:39

Did you check the detection logs when building the module ?

vishbynature · 7 Oct 2019, 05:44

@SGaist
I checked the process again.
on my ubuntu 16.04 host machine:
~/raspi/qt-everywhere-opensource-src-5.9.1/qtconnectivity$ ~/raspi/qt5/bin/qmake

Running configuration tests...
Done running configuration tests.

Configure summary:

Qt Bluetooth:
BlueZ .................................. no
BlueZ Low Energy ....................... no
Linux Crypto API ....................... no

Qt is now configured for building. Just run 'make'.
Once everything is built, Qt is installed.
You should NOT run 'make install'.
Note that this build cannot be deployed to other machines or devices.

Prior to reconfiguration, make sure you remove any leftovers from
the previous build.

"Note that this build cannot be deployed to other machines or devices."
well that's a bummer if its true.