Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. Mobile and Embedded
  4. Installing new module
Forum Updated to NodeBB v4.3 + New Features

Installing new module

Scheduled Pinned Locked Moved Unsolved Mobile and Embedded
ubuntu 16.04raspberry pi 3cross compileserial portnew module
26 Posts 4 Posters 6.6k Views 2 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • SGaistS SGaist

    Bluetooth support comes from the QtConnectivity module.

    V Offline
    V Offline
    vishbynature
    wrote on last edited by vishbynature
    #9

    @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.

    1 Reply Last reply
    0
    • SGaistS SGaist

      Bluetooth support comes from the QtConnectivity module.

      V Offline
      V Offline
      vishbynature
      wrote on last edited by
      #10

      @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?

      1 Reply Last reply
      0
      • SGaistS Offline
        SGaistS Offline
        SGaist
        Lifetime Qt Champion
        wrote on last edited by
        #11

        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.

        Interested in AI ? www.idiap.ch
        Please read the Qt Code of Conduct - https://forum.qt.io/topic/113070/qt-code-of-conduct

        V 1 Reply Last reply
        1
        • SGaistS SGaist

          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.

          V Offline
          V Offline
          vishbynature
          wrote on last edited by vishbynature
          #12

          @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?

          1 Reply Last reply
          0
          • SGaistS Offline
            SGaistS Offline
            SGaist
            Lifetime Qt Champion
            wrote on last edited by
            #13

            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 ?

            Interested in AI ? www.idiap.ch
            Please read the Qt Code of Conduct - https://forum.qt.io/topic/113070/qt-code-of-conduct

            V 1 Reply Last reply
            0
            • SGaistS SGaist

              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 ?

              V Offline
              V Offline
              vishbynature
              wrote on last edited by vishbynature
              #14

              @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. RoginaP 1 Reply Last reply
              0
              • V vishbynature

                @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. RoginaP Offline
                Pablo J. RoginaP Offline
                Pablo J. Rogina
                wrote on last edited by
                #15

                @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

                Upvote the answer(s) that helped you solve the issue
                Use "Topic Tools" button to mark your post as Solved
                Add screenshots via postimage.org
                Don't ask support requests via chat/PM. Please use the forum so others can benefit from the solution in the future

                V 1 Reply Last reply
                1
                • Pablo J. RoginaP Pablo J. Rogina

                  @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

                  V Offline
                  V Offline
                  vishbynature
                  wrote on last edited by
                  #16

                  @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?

                  1 Reply Last reply
                  0
                  • SGaistS Offline
                    SGaistS Offline
                    SGaist
                    Lifetime Qt Champion
                    wrote on last edited by
                    #17

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

                    Interested in AI ? www.idiap.ch
                    Please read the Qt Code of Conduct - https://forum.qt.io/topic/113070/qt-code-of-conduct

                    V 1 Reply Last reply
                    0
                    • SGaistS SGaist

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

                      V Offline
                      V Offline
                      vishbynature
                      wrote on last edited by
                      #18

                      @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.

                      V 1 Reply Last reply
                      0
                      • V vishbynature

                        @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.

                        V Offline
                        V Offline
                        vishbynature
                        wrote on last edited by
                        #19

                        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 .

                        1 Reply Last reply
                        0
                        • SGaistS Offline
                          SGaistS Offline
                          SGaist
                          Lifetime Qt Champion
                          wrote on last edited by
                          #20

                          Did you check the detection logs when building the module ?

                          Interested in AI ? www.idiap.ch
                          Please read the Qt Code of Conduct - https://forum.qt.io/topic/113070/qt-code-of-conduct

                          V 1 Reply Last reply
                          0
                          • SGaistS SGaist

                            Did you check the detection logs when building the module ?

                            V Offline
                            V Offline
                            vishbynature
                            wrote on last edited by
                            #21

                            @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.

                            jsulmJ 1 Reply Last reply
                            0
                            • V vishbynature

                              @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.

                              jsulmJ Offline
                              jsulmJ Offline
                              jsulm
                              Lifetime Qt Champion
                              wrote on last edited by
                              #22

                              @vishbynature said in Installing new module:

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

                              Looks like you still did not synchronise your sysroot...

                              https://forum.qt.io/topic/113070/qt-code-of-conduct

                              V 1 Reply Last reply
                              0
                              • jsulmJ jsulm

                                @vishbynature said in Installing new module:

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

                                Looks like you still did not synchronise your sysroot...

                                V Offline
                                V Offline
                                vishbynature
                                wrote on last edited by
                                #23

                                @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.

                                jsulmJ 1 Reply Last reply
                                0
                                • V vishbynature

                                  @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.

                                  jsulmJ Offline
                                  jsulmJ Offline
                                  jsulm
                                  Lifetime Qt Champion
                                  wrote on last edited by
                                  #24

                                  @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.

                                  https://forum.qt.io/topic/113070/qt-code-of-conduct

                                  V 1 Reply Last reply
                                  2
                                  • jsulmJ jsulm

                                    @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.

                                    V Offline
                                    V Offline
                                    vishbynature
                                    wrote on last edited by
                                    #25

                                    @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.

                                    jsulmJ 1 Reply Last reply
                                    0
                                    • V vishbynature

                                      @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.

                                      jsulmJ Offline
                                      jsulmJ Offline
                                      jsulm
                                      Lifetime Qt Champion
                                      wrote on last edited by
                                      #26

                                      @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.

                                      https://forum.qt.io/topic/113070/qt-code-of-conduct

                                      1 Reply Last reply
                                      1

                                      • Login

                                      • Login or register to search.
                                      • First post
                                        Last post
                                      0
                                      • Categories
                                      • Recent
                                      • Tags
                                      • Popular
                                      • Users
                                      • Groups
                                      • Search
                                      • Get Qt Extensions
                                      • Unsolved