Qt Embedded and tslib?

[wysota]

Where are the include files and libraries from tslib? Are they in /usr/lib or /usr/local/lib or where?

[newstead]

The libraries are in /usr/local/lib and include files in /usr/local/include

[wysota]

Does /usr/local/lib reside in your ld.so.conf? If not, you have to add it there and run ldconfig or pass appropriate flags to configure so that it looks for libraries there. By the way, probably placing the lib in /usr/local/lib doesn't make much sense if it is a library for architecture other than your native one. It'd be better if you created a separate directory structure for ARM files and pointed the configuration scripts to it.

[newstead]

Regardless of which path I place tslib in, do I get Qt to use it with the -L and -I flags when I configure Qt? Or is it something else I have missed?

Edit: Yes, /usr/local/lib resides in ld.so.conf

[wysota]

What does ldd on the tslib return?

[newstead]

"not a dynamically executable binary"
Or what it could look like in english


Edit: Are there any other options beside tslib for using Qt on an ARM embedded system?

Have to edit again.... this is what i get with ldd now:
libdl.so.2 => /lib/libdl.so.2 (0x4000b000)
libc.so.6 => /lib/libc.so.6 (0x40016000)
/lib/ld-linux.so.3 (0x2a000000)

[wysota]

This looks like a library compiled for your system, not for ARM.

[newstead]

This looks like a library compiled for your system, not for ARM.

That's from running ldd on the ARM-board. Running ldd on the same file at my host brings the "not an executable..." message

If I run "file libts-0.0.so.0.1.1" I get:
libts-0.0.so.0.1.1: ELF 32-bit LSB shared object, ARM, version 1 (SYSV), dynamically linked, not stripped
So it's definitely compiled for the ARM-arch. Therefore, the question still remains: How do I use tslib from Qt?

[wysota]

You need to point Qt's configure script to tslib's include files and you need the tslib library available in a place where the linker can find it.

[newstead]

You need to point Qt's configure script to tslib's include files and you need the tslib library available in a place where the linker can find it.

I'm past that now. It seems however that there is some problems not related to Qt since these commands:

mknod /dev/input/event1 c 13 65
rm -f /etc/pointercal
 
export TSLIB_CONSOLEDEVICE=none
export TSLIB_FBDEVICE=/dev/fb0
export TSLIB_TSDEVICE=/dev/input/event1
export TSLIB_CALIBFILE=/etc/pointercal
export TSLIB_CONFFILE=/usr/etc/ts.conf
export TSLIB_PLUGINDIR=/usr/lib/ts
 
export LD_LIBRARY_PATH=/usr/lib

mknod /dev/input/event1 c 13 65
rm -f /etc/pointercal

export TSLIB_CONSOLEDEVICE=none
export TSLIB_FBDEVICE=/dev/fb0
export TSLIB_TSDEVICE=/dev/input/event1
export TSLIB_CALIBFILE=/etc/pointercal
export TSLIB_CONFFILE=/usr/etc/ts.conf
export TSLIB_PLUGINDIR=/usr/lib/ts

export LD_LIBRARY_PATH=/usr/lib

To copy to clipboard, switch view to plain text mode 

results in:

xres = 480, yres = 640
selected device is not a touchscreen I understand

xres = 480, yres = 640
selected device is not a touchscreen I understand

To copy to clipboard, switch view to plain text mode 

Even though it might not belong in a Qt-forum, maybe you have an idea why tslib doesn't recognise the device as a touchscreen?

[wysota]

I have no experience in using tslib, so no, I don't have any idea. I might guess that either the event source (/dev/input/event*) or the kernel module is not configured/running properly.

[newstead]

Problem solved. It actually turned out to be a HW-error but thanks for your help anyway!