tslib

For reference, I'm running Ubuntu 9.04

1. Install Iibtool. Use whatever package manager is used for your distro. For example "sudo apt-get install libtool" on Ubuntu. Since this package isn't necessarily installed by default, and it isn't needed for building apps or the kernel, you may not have this already.
2. Forget about the archived downloads. Not only for this thread, but other posts I've dug up around the web contain instructions that for some reason, just don't work on my system. Head straight to CVS. (Of course, if you do not have CVS, install it first. e.g. "sudo apt-get install cvs")
       export CVSROOT=:pserver:anoncvs@cvs.handhelds.org:/cvs
       cvs login
       cvs co apps/tslib
   When asked for a password, use "anoncvs". The final command will just checkout a copy of the source code into whatever directory you are in right now.
3. Do as described in the document above about exporting the environment variables, if you have not done so already:
       export CC=/opt/omap3evm/toolchain/arm-2007q3/bin/arm-none-linux-gnueabi-gcc
       export CXX=/opt/omap3evm/toolchain/arm-2007q3/bin/arm-none-linux-gnueabi-g++
       export CONFIG_SITE=omap3evm.autogen
   Of course, replace the paths in the CC and CXX variables with wherever you placed the compiler (which will probably be similar to above depending on which version of the EVM User Manual you've been following).
4. Drill down to the apps/tslib directory and enter the command:
        ./autogen.sh
   this should create a "configure" file which you can then run
5. Don't just run "./configure", you will need some switches:
       ./configure --build=i386-linux --host=arm-none-linux-gnueabi target=arm --prefix=/omapevm_nfs
   The last switch "--prefix" just tells it where to dump the output files after you run "make". If you have NFS setup to the EVM (or whatever board you're using), it will be easiest to dump it there. Otherwise, you can also dump it into any directory on your host. You will just have to transfer it over to the EVM later. (For example, in my case, I need to create the entire filesystem to be flashed into NAND anyways, so I will dump it on my host first).
6. Now you can run the make and install
       make
       make install
7. At this point, you can continue to basically follow the guide pointed at by the original post.
   Find where you dumped the output files (in the above case, /omapevm_nfs) and dig into the "etc" directory to edit the "ts.conf" file. As described in the above guide, uncomment the line that says "module_raw input".
8. On the EVM, that is, when you are booted at the command line and you're running Linux from OMAP, add these environment variables:
       export TSLIB_FBDEVICE=/dev/fb0
       export TSLIB_TSDEVICE=/dev/input/event1
       export TSLIB_CONFFILE=/etc/ts.conf
       export TSLIB_CALIBFILE=/etc/pointercal
       export TSLIB_CONSOLEDEVICE=none
9. run "ts_calibrate" on the OMAP EVM. This file should've been populated after "make install". If you have dumped the files onto the host, then you will have to transfer not only this file, but also the lib files over. Basically copy everything that resulted from "make install". You should see 4 directories "bin", "etc", "include" and "lib", so to be safe, copy the contents over to the EVM (i.e. /bin, /etc, /include and /lib respectively). Of course, if you have setup an NFS file system on your EVM, you won't have to do this.