Installing new module
-
Bluetooth support comes from the QtConnectivity module.
-
@SGaist,
ok, I will make QtConnectivity module. -
@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.
-
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.
-
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.
@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? -
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 ?
-
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 ?
@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. -
@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.@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 wellso whenever you install libraries/headers in your device, you need to keep it in sync in the sysroot folder in your host
-
@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 wellso whenever you install libraries/headers in your device, you need to keep it in sync in the sysroot folder in your host
@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? -
@Pablo-J-Rogina already provided the answer in italic: rsync.
-
@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. -
@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.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 . -
Did you check the detection logs when building the module ?
-
@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/qmakeRunning configuration tests...
Done running configuration tests.Configure summary:
Qt Bluetooth:
BlueZ .................................. no
BlueZ Low Energy ....................... no
Linux Crypto API ....................... noQt 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. -
@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/qmakeRunning configuration tests...
Done running configuration tests.Configure summary:
Qt Bluetooth:
BlueZ .................................. no
BlueZ Low Energy ....................... no
Linux Crypto API ....................... noQt 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.@vishbynature said in Installing new module:
Qt Bluetooth:
BlueZ .................................. no
BlueZ Low Energy ....................... no
Linux Crypto API ....................... noLooks like you still did not synchronise your sysroot...
-
@vishbynature said in Installing new module:
Qt Bluetooth:
BlueZ .................................. no
BlueZ Low Energy ....................... no
Linux Crypto API ....................... noLooks like you still did not synchronise your sysroot...
@jsulm
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.ok what exactly i need to do to synchronise my sysroot.
-
@jsulm
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.ok what exactly i need to do to synchronise my sysroot.
@vishbynature Please take a look at configure log to see what exactly is missing. Configure compiles some simple code snippets to check each functionality and if for example it fails to compile becuse of missing header file you will see this in the log.
-
@vishbynature Please take a look at configure log to see what exactly is missing. Configure compiles some simple code snippets to check each functionality and if for example it fails to compile becuse of missing header file you will see this in the log.
@jsulm
ok this might be silliest thing to say but I don't know where to find configure log to see whats missing. In the build folder i searched for config.log that i had number of files pop-up from different directories i didn't understand them. -
@jsulm
ok this might be silliest thing to say but I don't know where to find configure log to see whats missing. In the build folder i searched for config.log that i had number of files pop-up from different directories i didn't understand them.@vishbynature It's config.log file located in the same directory from which you called configure. It is a text file, nothing special. Look for compile errors in that file related to to what you need.
