This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Setting up Tslib and Qt / tslib functionality test failed

Hello:

I have seen

http://processors.wiki.ti.com/index.php/Building_Qt

http://processors.wiki.ti.com/index.php/Tslib

http://processors.wiki.ti.com/index.php/Qt_Tips

file://///Hp28828165791/shareddocs/share/ti_L138/qt-embedded-crosscompiling.html

I have also seen and read…

http://e2e.ti.com/support/dsp/omap_applications_processors/f/447/p/29529/143292.aspx#143292
http://e2e.ti.com/cfs-file.ashx/__key/CommunityServer.Components.UserFiles/00.00.01.17.26/HowToQTEmbedded.pdf

I have installed the Tslib (remember,  this is OMAP-L138 so paths names are sightly different etc.)

I have been attempting next to Install Qt embedded…

In Miak’s HowToQTEmbedded.pdf he mentions in step 4. note:
this should run through without any error messages. Make sure that
the tslib functionality test does not fail.

Well, it is failing as in
The tslib functionality test failed! You might need to modify the include and library search paths by editing QMAKE_INCDIR and QMAKE_LIBDIR in

————————————————————————————————
My configure parameters to qt are
./configure -prefix /home/user/qt-everywhere-opensource-src-4.6.3/install_2/qt -platform /qws/linux-x86-g++ -xplatform /qws/linux-arm-g++ -embedded arm -no-openssl -no-cups -qt-mouse-pc -no-qt3support -qt-mouse-tslib -qt-libjpeg -no-phonon -no-largefile
————————————————————————————————
my qmake.conf reads
#

  1. qmake configuration for building with arm-linux-g++


#

include(../../common/g++.conf)
include(../../common/linux.conf)
include(../../common/qws.conf)

#modifications to include ts-lib
QMAKE_INCDIR += /home/user/qt-everywhere-opensource-src-4.6.3/install_2/include
QMAKE_LIBDIR += /home/user/qt-everywhere-opensource-src-4.6.3/install_2/lib

  1. modifications to g++.conf
    QMAKE_CFLAGS_RELEASE = -O3 -march=armv9e -mfpu=fpe2 -mfloat-abi=softfp
    QMAKE_CXXFLAGS_RELEASE = -O3 -march=armv9e -mfpu=fpe2 -mfloat-abi=softfp

QMAKE_CC = /home/user/CodeSourcery/Sourcery_G++_Lite/bin/arm-none-linux-gnueabi-gcc
QMAKE_CXX = /home/user/CodeSourcery/Sourcery_G++_Lite/bin/arm-none-linux-gnueabi-g++
QMAKE_LINK = /home/user/CodeSourcery/Sourcery_G++_Lite/bin/arm-none-linux-gnueabi-g++
QMAKE_LINK_SHLIB = /home/user/CodeSourcery/Sourcery_G++_Lite/bin/arm-none-linux-gnueabi-g++

QMAKE_AR = /home/user/CodeSourcery/Sourcery_G++_Lite/bin/arm-linux-ar cqs
QMAKE_OBJCOPY = /home/user/CodeSourcery/Sourcery_G++_Lite/bin/arm-linux-objcopy
QMAKE_STRIP = /home/user/CodeSourcery/Sourcery_G++_Lite/bin/arm-linux-strip

load(qt_config)
————————————————————————————————

The files located at QMAKE_INCDIR are
user@user-desktopUbuntuLTS:~/qt-everywhere-opensource-src-4.6.3/install_2/include$ ls
tslib.h

and QMAKE_LIBDIR
user@user-desktopUbuntuLTS:~/qt-everywhere-opensource-src-4.6.3/install_2/lib$ ls
libts-0.0.so.0 libts-0.0.so.0.1.1 libts.la libts.so pkgconfig ts

————————————————————————————————
As mentioned in ttp://e2e.ti.com/support/dsp/omap_applications_processors/f/447/p/29529/143292.aspx#143292
Miak’s HowToQTEmbedded.pdf he mentios in step 4. note:
this should run through without any error messages. Make sure that
the tslib functionality test does not fail.

Unfortunately nowhere have I found out what to do about it if it does fail…?
Can anyone help..
Are my configure parameters to qt wrong ?
My qmake.conf wrong ?

Please ask for any more information you need to help me.

Please advise, there really is nothing different then a “stranded” qt configure setup procedures… I think?

Thanks

 

  • The direction for Qt is as follows... everyone has seen this...

    ===================================================================

    You might need to modify the include and library search paths by editing
     QMAKE_INCDIR and QMAKE_LIBDIR in
    /home//QT/qt-everywhere-opensource-src-4.8.4/mkspecs/qws/linux-arm-gnueabi-g++

    ===================================================================

    Of course this is silly, how can one add an environment variable to a directory?

    Bad Qt... Bad Qt.

    So, getting past that, if one does add the correct entries in the relevant qmake.conf, in the directory

    indicated by Qt, one still gets the error.

    Apparently you have to dig through the Qt source and figure this one out for yourself.

    There is apparently no valid help for you and the many hundreds... perhaps thousands of you on the net.

    Open Source help via the web is difficult and getting harder by the day... as everything changes, the old valid help that is on the web

    becomes invalid. In time, the number of wrong answers will out number the correct one or two

    answers by the thousands.