Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt
  • Unsolved
Collapse
qtws26_logo

The Qt Event of the Year: Qt World Summit 2026

Save Your Spot >
Brand Logo
  1. Home
  2. Qt Development
  3. Mobile and Embedded
  4. EGalax touchscreen and Qt5
Qt 6.12 LTS is out! See what's new in the release blog

EGalax touchscreen and Qt5

Scheduled Pinned Locked Moved Mobile and Embedded
33 Posts 6 Posters 42.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.
  • T Offline
    T Offline
    Tannyveer
    wrote on last edited by
    #8

    Hi sid,
    When i a modified the qmake.conf file what u post i got the follwoing error

    /home/tal/opt/gcc-4.7-linaro-rpi-gnueabihf/bin/../lib/gcc/arm-linux-gnueabihf/4.7.2/../../../../arm-linux-gnueabihf/include/c++/4.7.2/arm-linux-gnueabihf/bits/os_defines.h:40:22: fatal error: features.h: No such file or directory
    compilation terminated.
    make: *** [.obj/qtslib.o] Error 1

    1 Reply Last reply
    0
    • S Offline
      S Offline
      Sidii
      wrote on last edited by
      #9

      Hi Tannyveer,

      Lets start from the beginning, First we need to build TSLIB. i will tell you whatever i did. Let me know wheter you are done with these steps or not.

      For TSLIB:
      @
      export ac_cv_func_malloc_0_nonnull=yes
      export CC=powerpc-wrs-linux-gnu-ppc_603e-glibc_std-gcc
      export CXX=powerpc-wrs-linux-gnu-ppc_603e-glibc_std-g++
      @

      If you get a problem about an undefined reference to rpl_malloc, you
      probably need to do:
      @$ export ac_cv_func_malloc_0_nonnull=yes@
      CC and CXX is your compiler. (In my case it is cross compilation so i gave the power pc tool chain compiler)

      After that:

      @
      ./autogen.sh
      ./configure --host=powerpc-603e-linux --target=powerpc --prefix=/usr/local
      make
      make install
      @
      You need to modify --host and --target as per your system. --prefix is the path where the final library will be generated.

      If all OK, you will get following summary:

      @
      ./configure --host=powerpc-603e-linux --target=powerpc --prefix=/usr/local
      configure: WARNING: If you wanted to set the --build type, don't use --host.
      If a cross compiler is detected then cross compile mode will be used.
      checking for a BSD-compatible install... /usr/bin/install -c
      checking whether build environment is sane... yes
      checking for powerpc-603e-linux-strip... no
      checking for strip... strip
      checking for a thread-safe mkdir -p... /bin/mkdir -p
      checking for gawk... gawk
      checking whether make sets $(MAKE)... yes
      checking whether the C++ compiler works... yes
      checking for C++ compiler default output file name... a.out
      checking for suffix of executables...
      checking whether we are cross compiling... yes
      checking for suffix of object files... o
      checking whether we are using the GNU C++ compiler... yes
      checking whether powerpc-wrs-linux-gnu-ppc_603e-glibc_std-g++ accepts -g... yes
      checking for style of include used by make... GNU
      checking dependency style of powerpc-wrs-linux-gnu-ppc_603e-glibc_std-g++... gcc3
      checking for powerpc-603e-linux-gcc... powerpc-wrs-linux-gnu-ppc_603e-glibc_std-gcc
      checking whether we are using the GNU C compiler... yes
      checking whether powerpc-wrs-linux-gnu-ppc_603e-glibc_std-gcc accepts -g... yes
      checking for powerpc-wrs-linux-gnu-ppc_603e-glibc_std-gcc option to accept ISO C89... none needed
      checking dependency style of powerpc-wrs-linux-gnu-ppc_603e-glibc_std-gcc... gcc3
      checking how to run the C preprocessor... powerpc-wrs-linux-gnu-ppc_603e-glibc_std-gcc -E
      checking whether the C compiler supports -fvisibility=hidden... yes
      checking whether to use -fvisibility=hidden... yes
      checking whether ln -s works... yes
      checking whether make sets $(MAKE)... (cached) yes
      checking build system type... i686-pc-linux-gnu
      checking host system type... powerpc-603e-linux-gnu
      checking for a sed that does not truncate output... /bin/sed
      checking for grep that handles long lines and -e... /bin/grep
      checking for egrep... /bin/grep -E
      checking for fgrep... /bin/grep -F
      checking for ld used by powerpc-wrs-linux-gnu-ppc_603e-glibc_std-gcc... /opt/WindRiver40/wrlinux-4/layers/wrll-toolchain-4.4a-323/powerpc/toolchain/x86-linux2/powerpc-wrs-linux-gnu/bin/ld
      checking if the linker (/opt/WindRiver40/wrlinux-4/layers/wrll-toolchain-4.4a-323/powerpc/toolchain/x86-linux2/powerpc-wrs-linux-gnu/bin/ld) is GNU ld... yes
      #Removed lots of stuffs here due to 6000 characters limit
      checking for vprintf... yes
      checking for _doprnt... no
      checking for bzero... yes
      checking for gettimeofday... yes
      checking for memmove... yes
      checking for memset... yes
      checking for munmap... yes
      checking for select... yes
      checking for strcasecmp... yes
      checking for strchr... yes
      checking for strdup... yes
      checking for strtoul... yes
      checking whether linear modules is requested... yes
      checking whether dejitter module is requested... yes
      checking whether linear-h2200 module is requested... yes
      checking whether variance module is requested... yes
      checking whether pthres module is requested... yes
      checking whether ucb1x00 module is requested... yes
      checking whether corgi module is requested... yes
      checking whether collie module is requested... yes
      checking whether h3600 module is requested... yes
      checking whether mk712 module is requested... yes
      checking whether arctic2 module is requested... yes
      checking whether input module is requested... yes
      checking where to place modules... ${libdir}/ts/
      checking whether to enable debugging... no
      configure: creating ./config.status
      config.status: creating Makefile
      config.status: creating etc/Makefile
      config.status: creating plugins/Makefile
      config.status: creating src/Makefile
      config.status: creating tests/Makefile
      config.status: creating tslib-0.0.pc
      config.status: creating config.h
      config.status: executing depfiles commands
      config.status: executing libtool commands
      root@ebx-all:/usr/local/QT_littlee/qt-everywhere-opensource-src-5.2.1/qtbase/bin/tslib-1.0 #
      @

      Let me know if you are done with this. Then we will proceed with the intagration of TSLIB with the QT5

      1 Reply Last reply
      0
      • T Offline
        T Offline
        Tannyveer
        wrote on last edited by
        #10

        Hi Sid
        Thanks for ur above post i succesfully compile the tslib plugin.
        but my problem cannot be solved :
        Still touchscreen cannot be respond my Qt application.

        I am using Raspberry Pi board:
        Qt5 Installed:
        Raspbian Os
        egalax touch screen also installed
        tslib i.e libqtslibplugin.so in my qtinstalled path
        I also removed libqevtouchplugin.so in the generic path

        1 Reply Last reply
        0
        • S Offline
          S Offline
          Sidii
          wrote on last edited by
          #11

          Hi Tannyveer,
          Are you able to run some TSLIB tools like:

          1. ts_test
          2. ts_calibration

          If above tools work fine then you can say that TSLIB is successfully installed.

          Then we will look into the integration of TSLIB with QT5

          1 Reply Last reply
          0
          • T Offline
            T Offline
            Tannyveer
            wrote on last edited by
            #12

            hi sid

            i compiled tslib on my host system then copy the liqtslibplugin.so in my target raspberri pi system i.e in Qt_installed/plugins/generic folder.

            ts_test
            ts-calibration commands
            was not found in my taget system.

            1 Reply Last reply
            0
            • S Offline
              S Offline
              Sidii
              wrote on last edited by
              #13

              Hello Tannyveer,

              TSLIB is a separate from QT, you need to download the source code and then compile it. Download it from here:
              http://sourceforge.net/projects/tslib.berlios/

              1 Reply Last reply
              0
              • T Offline
                T Offline
                Tannyveer
                wrote on last edited by
                #14

                hi sid
                whether tslib compile in my target system ie my rsapberry pi or compile in my host system i am confused if it is in host system im already compiled.

                1 Reply Last reply
                0
                • S Offline
                  S Offline
                  Sidii
                  wrote on last edited by
                  #15

                  Hi Tannyveer,
                  If you have already compiled tslib library for RPI then there must be some tools generated along with the compilation. Check "tests" folder. If those tools like ts_test, ts_calibrate works fine then that means your tslib is working fine.

                  If you compiled TSLIB in host system then transfer the required tools to RPI and then try running them.

                  Thanks

                  1 Reply Last reply
                  0
                  • T Offline
                    T Offline
                    Tannyveer
                    wrote on last edited by
                    #16

                    when i run
                    ./ts_test and ./ts_calibration i got the following error
                    libts-1.0.so.0: cannot open shared object file: No such file or directory
                    in my RPI

                    1 Reply Last reply
                    0
                    • S Offline
                      S Offline
                      Sidii
                      wrote on last edited by
                      #17

                      Ok then copy these libraries into your RPI and then add the path to environment variable LD_LIBRARY_PATH.

                      If you generated the tslib in your host pc, then they get generated inside /usr/local.

                      Copy these .so files to your RPI and add the path to LD_LIBRARY_PATH.

                      let me know what happens next.

                      1 Reply Last reply
                      0
                      • T Offline
                        T Offline
                        Tannyveer
                        wrote on last edited by
                        #18

                        i add the path and i got the illegal operation error when i run ./ts_test

                        1 Reply Last reply
                        0
                        • S Offline
                          S Offline
                          Sidii
                          wrote on last edited by
                          #19

                          Have you set the following environment variables:

                          @
                          export TSLIB_FBDEVICE=/dev/fb0
                          export TSLIB_TSDEVICE=/dev/ttyS1
                          export TSLIB_PLUGINDIR=/home/Sid/tslib_plugins
                          export TSLIB_CONFFILE=/home/Sid/ts.conf
                          @

                          also try running ts_calibrate. Do you get same error?

                          Also some more tools are present like ts_print, ts_print_raw.

                          Try running them as well..

                          1 Reply Last reply
                          0
                          • T Offline
                            T Offline
                            Tannyveer
                            wrote on last edited by
                            #20

                            hi sid
                            so sadly i got the same error when i test the ts-test ts_calibrate ts_print ts_print-raw tools

                            1 Reply Last reply
                            0
                            • S Offline
                              S Offline
                              Sidii
                              wrote on last edited by
                              #21

                              Dear Tannyveer,

                              I think may be its is related to some permission issue. I am not sure.
                              Try changing the permission of all the related files.

                              Also check with ldd command whether all the libraries needed are found by the required binaries or not.
                              i have not come across any such error :(

                              1 Reply Last reply
                              0
                              • T Offline
                                T Offline
                                Tannyveer
                                wrote on last edited by
                                #22

                                Dear Sid
                                sorry for the late post i am out of station from three days, right now iam in my workbench still i got the same errors i want to compile the tslib once again
                                now my question is iam compiling tslib on my host system contains ubuntu 14.04 32-bit version. Is any problem encounter with this desktop version.
                                another queston after install tslib in my host system i transfered the install files using gftp.this may be any troubled for my tslib.

                                please answers these questions so that i vl try again to compile the tslib. give me the procedure from first steps to compile the tslib

                                1 Reply Last reply
                                0
                                • S Offline
                                  S Offline
                                  Sidii
                                  wrote on last edited by
                                  #23

                                  So you are cross compiling. I mean to say you are compiling the source code in Ubuntu and then deploying the binaries in the RPI?

                                  If this is the case then you are doing cross compilation. Is it true?

                                  1 Reply Last reply
                                  0
                                  • T Offline
                                    T Offline
                                    Tannyveer
                                    wrote on last edited by
                                    #24

                                    yep sid

                                    1 Reply Last reply
                                    0
                                    • T Offline
                                      T Offline
                                      Tannyveer
                                      wrote on last edited by
                                      #25

                                      Dear Sid,
                                      Is there any method along with this. please post me Sid

                                      1 Reply Last reply
                                      0
                                      • S Offline
                                        S Offline
                                        Sidii
                                        wrote on last edited by
                                        #26

                                        Do following steps:

                                        @
                                        export ac_cv_func_malloc_0_nonnull=yes
                                        export CC=powerpc-wrs-linux-gnu-ppc_603e-glibc_std-gcc
                                        export CXX=powerpc-wrs-linux-gnu-ppc_603e-glibc_std-g++
                                        ./autogen.sh
                                        ./configure --host=powerpc-603e-linux --target=powerpc --prefix=/usr/local
                                        make
                                        make install
                                        @

                                        Make necessary changes in line number 2,3,5 as per your RPI tool chain. If you get a problem about an undefined reference to rpl_malloc, then only you need to do line number 1.

                                        1 Reply Last reply
                                        0
                                        • T Offline
                                          T Offline
                                          Tannyveer
                                          wrote on last edited by
                                          #27

                                          dear sid
                                          i installed the tslib on my rpi when i run ts_test and ts_calibrate
                                          i got the following

                                          couldnot load loaded pthres
                                          No raw modules
                                          ts_config :Sucess

                                          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
                                          • Unsolved