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. Deploying program error with QT everywhere
Forum Updated to NodeBB v4.3 + New Features

Deploying program error with QT everywhere

Scheduled Pinned Locked Moved Unsolved Mobile and Embedded
20 Posts 2 Posters 6.1k Views 1 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 Offline
    SGaistS Offline
    SGaist
    Lifetime Qt Champion
    wrote on last edited by
    #2

    Hi,

    If you call ldd on your executable on your target, what do you get ?

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

    Z 1 Reply Last reply
    0
    • Z Offline
      Z Offline
      zdenekrejci
      wrote on last edited by
      #3
      This post is deleted!
      1 Reply Last reply
      0
      • SGaistS SGaist

        Hi,

        If you call ldd on your executable on your target, what do you get ?

        Z Offline
        Z Offline
        zdenekrejci
        wrote on last edited by
        #4

        @SGaist olimex@a13-OLinuXino-Micro:~$ ldd /home/olimex/untitled5
        /home/olimex/untitled5: /lib/arm-linux-gnueabihf/libc.so.6: version GLIBC_2.15' not found (required by /usr/local/qt/lib/libQtCore.so.4) /home/olimex/untitled5: /lib/arm-linux-gnueabihf/libc.so.6: version GLIBC_2.15' not found (required by /usr/local/qt/lib/libQtNetwork.so.4)
        libQtGui.so.4 => /usr/local/qt/lib/libQtGui.so.4 (0xb688b000)
        libQtCore.so.4 => /usr/local/qt/lib/libQtCore.so.4 (0xb662a000)
        libstdc++.so.6 => /usr/lib/arm-linux-gnueabihf/libstdc++.so.6 (0xb6571000)
        libgcc_s.so.1 => /lib/arm-linux-gnueabihf/libgcc_s.so.1 (0xb654d000)
        libc.so.6 => /lib/arm-linux-gnueabihf/libc.so.6 (0xb6466000)
        /lib/ld-linux-armhf.so.3 (0xb6f1d000)
        libQtNetwork.so.4 => /usr/local/qt/lib/libQtNetwork.so.4 (0xb63be000)
        libpthread.so.0 => /lib/arm-linux-gnueabihf/libpthread.so.0 (0xb63a2000)
        libm.so.6 => /lib/arm-linux-gnueabihf/libm.so.6 (0xb6337000)
        libdl.so.2 => /lib/arm-linux-gnueabihf/libdl.so.2 (0xb632c000)
        librt.so.1 => /lib/arm-linux-gnueabihf/librt.so.1 (0xb631e000)

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

          Looks like you are using a sysroot for building that doesn't match the one from your target.

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

          Z 1 Reply Last reply
          1
          • SGaistS SGaist

            Looks like you are using a sysroot for building that doesn't match the one from your target.

            Z Offline
            Z Offline
            zdenekrejci
            wrote on last edited by zdenekrejci
            #6

            @SGaist not sure if I fully understand, so what should I do? set somwhere sysroot?
            I found settings in QT creator for sysroot, is that what you mentioned?
            0_1520163093643_Screenshot from 2018-03-04 12-25-43.png

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

              No, I mean that you should cross-compile Qt using a sysroot that matches the one from your device.

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

              Z 1 Reply Last reply
              1
              • SGaistS SGaist

                No, I mean that you should cross-compile Qt using a sysroot that matches the one from your device.

                Z Offline
                Z Offline
                zdenekrejci
                wrote on last edited by
                #8

                @SGaist do you mean qt creator or qt everywhere? if qt everywhere than here is what I used for configure and make>
                Last configuration used for compiling qt everywhere

                make clean; ./configure -embedded arm -prefix /usr/local/qt -little-endian -no-qt3support -no-cups -no-largefile -optimized-qmake -no-openssl -nomake tools -nomake examples -no-webkit -opensource -confirm-license

                make used> make -j 5

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

                  Not Qt Creator, it's just the IDE and you don't need to cross-compile it unless you plan to run in on your target.

                  How did you install your cross-compiler ?

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

                  1 Reply Last reply
                  0
                  • Z Offline
                    Z Offline
                    zdenekrejci
                    wrote on last edited by
                    #10

                    Iam now a litle bit confused.. you say not the qt creator but IDE... isnt QT equals IDE???

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

                      No, Qt Creator is the name of the cross-platform IDE the Qt Company is developing for developers. Qt itself is a pretty large framework.

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

                      Z 1 Reply Last reply
                      0
                      • SGaistS SGaist

                        No, Qt Creator is the name of the cross-platform IDE the Qt Company is developing for developers. Qt itself is a pretty large framework.

                        Z Offline
                        Z Offline
                        zdenekrejci
                        wrote on last edited by
                        #12

                        @SGaist Hi, still trying to make it work whenever I have a little bit time. Iam trying different versions of qt everywhere. Also would have a question, what is the differene between qt-everywhere and qt-embedded? is it only about different name or there is something else?

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

                          If you are referring to the package name, yes. Qt Embedded was meant for devices without X server providing QWS. Qt everywhere is for all supported devices.

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

                          Z 2 Replies Last reply
                          0
                          • SGaistS SGaist

                            If you are referring to the package name, yes. Qt Embedded was meant for devices without X server providing QWS. Qt everywhere is for all supported devices.

                            Z Offline
                            Z Offline
                            zdenekrejci
                            wrote on last edited by zdenekrejci
                            #14

                            @SGaist Next test>
                            I have no package none-gnueabi so I deleted the "none" from
                            mkspecs/qws/linux-arm-gnueabi-g++/qmake.conf

                            the problem i thing could be still that in qt creator i can see the name of the
                            compiler is
                            arm-linux-gnueabi-g++ in my host system
                            but the one that I can select in qt-everywhere ...mkspecs/qws/ is
                            linux-arm-gnueabi-g++

                            anyway Iam going to try to configure and make

                            ./configure -embedded arm -prefix /usr/local/qt4-7.3 -little-endian -no-qt3support -no-cups -no-largefile -optimized-qmake -no-openssl -nomake tools -nomake examples -no-webkit -opensource -confirm-license -xplatform qws/linux-arm-gnueabi-g++

                            make
                            make install

                            compiled and installed
                            QT creator showing on run
                            bash: /home/olimex/untitled8: No such file or directory
                            Application finished with exit code 127.

                            and if I try create non qt in qt creator like standard console application everything is ok i can build and deploy on target.

                            back to qt application, if I try ldd on executable on target I get nothing...? Somehow is the qt-everywhere not working... I thign... Any ideas?

                            1 Reply Last reply
                            0
                            • SGaistS SGaist

                              If you are referring to the package name, yes. Qt Embedded was meant for devices without X server providing QWS. Qt everywhere is for all supported devices.

                              Z Offline
                              Z Offline
                              zdenekrejci
                              wrote on last edited by
                              #15

                              @SGaist There is also one thing I found in settings for the compiler there is parametr arm-linux-generic-32-bit itsnt this the problem? should not be there something like i386 or different? The board onlinuxino with armv7 is not 32bit..so?

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

                                That's the cross-compiler, it indicates the target for which it will compile your application.

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

                                Z 1 Reply Last reply
                                0
                                • SGaistS SGaist

                                  That's the cross-compiler, it indicates the target for which it will compile your application.

                                  Z Offline
                                  Z Offline
                                  zdenekrejci
                                  wrote on last edited by zdenekrejci
                                  #17

                                  @SGaist I know its indicating the target but my target is not 32bit as far as I know.
                                  armv7 is not 32 or 64. Thats what I have read in different forum. So what I ask is
                                  "should not be there something like i386 or different?" in the compiler settings?

                                  And when I try to compile qt-everywhere version 4.7.3 with compiler arm-linux-gnueabi-cpp and try to run it on target it gives me output

                                  bash: /home/olimex/untitled11: No such file or directory
                                  Application finished with exit code 127.

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

                                    What does file /home/olimex/untitled11 tell you ?

                                    i386 is for Intel/AMD processor. ARM is also available in 32 and 64bit architecture.

                                    What is your target board exactly ?

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

                                    Z 1 Reply Last reply
                                    1
                                    • SGaistS SGaist

                                      What does file /home/olimex/untitled11 tell you ?

                                      i386 is for Intel/AMD processor. ARM is also available in 32 and 64bit architecture.

                                      What is your target board exactly ?

                                      Z Offline
                                      Z Offline
                                      zdenekrejci
                                      wrote on last edited by
                                      #19

                                      @SGaist
                                      What you mean by "What does file /home/olimex/untitled11 tell you ?"
                                      the ouptut when I call it is bash: /home/olimex/untitled11: No such file or directory
                                      Application finished with exit code 127.

                                      Here is the Board

                                      FEATURES

                                      A13 Cortex A8 processor at 1GHz, 3D Mali400 GPU
                                      256 MB RAM (128Mbit x 16)
                                      5VDC input power supply with own ICs, noise immune design
                                      1 USB host
                                      1 USB OTG which can power the board
                                      SD-card connector for booting the Linux image
                                      VGA video output
                                      LCD signals available on connector so you still can use LCD if you disable VGA/HDMI
                                      Audio output
                                      Microphone input pads (no connector)
                                      1 User key
                                      4 Mount holes
                                      UEXT connectorfor connecting additional UEXT modules like Zigbee, Bluetooth, Relays, etc
                                      GPIO connector with 68/74 pins and these signals:
                                          17 for adding NAND flash;
                                          22 for connecting LCDs;
                                          20+4 including 8 GPIOs which can be input, output, interrupt sources;
                                          3x I2C;
                                          2x UARTs;
                                          SDIO2 for connecting SDcards and modules;
                                          5 system pins: +5V, +3.3V, GND, RESET, NMI
                                      Dimensions: 100 x 85 mm (3.950x3.350'')
                                      Optional low-cost 7" LCD with touchscreen
                                      

                                      https://www.olimex.com/Products/OLinuXino/A13/A13-OLinuXino-MICRO/open-source-hardware

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

                                        Then it means that the file wasn't copied over to the target.

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

                                        1 Reply Last reply
                                        0

                                        • Login

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