From: Mark B. <ma...@at...> - 2008-08-20 13:29:21
|
Hi All, I have some trouble getting directfb to use tslib for the Samsung display and touchscreen. Using OE, I built a directfb version with tslib support ( added --with-inputdrivers=tslib to EXTRA_OECONF) and it all installed just fine. Unfortunately I did not see any input support show up in the directfb debug output messages. Here is what I am getting: =======================| DirectFB 1.1.0 |======================= (c) 2001-2007 The DirectFB Organization (directfb.org) (c) 2000-2004 Convergence (integrated media) GmbH ------------------------------------------------------------ (*) DirectFB/Core: Single Application Core. (2008-08-19 19:49) (*) Direct/Thread: Running 'VT Switcher' (CRITICAL, 812)... (!) Direct/Modules: Could not open module directory `/usr/lib/directfb-1.1-0/gfxdrivers'! --> No such file or directory (*) DirectFB/Graphics: Generic Software Rasterizer 0.6 (directfb.org) (*) DirectFB/Core/WM: Default 0.3 (directfb.org) (*) FBDev/Mode: Testing 480x272 RGB16 (*) FBDev/Mode: Preparing switch to 480x272 RGB16 (*) FBDev/Mode: Testing 480x272 RGB16 (*) FBDev/Mode: Preparing switch to 480x272 RGB16 I did set up the TSLIB variables and tslib itself seems to be working just fine. I am able to run the calibrate and test programs. Using OE version 318. Anyone able to get it to play or am I missing something key? Thanks Mark |
From: Mark B. <ma...@at...> - 2008-08-21 14:03:36
|
Mark Barton wrote: > Hi All, > I have some trouble getting directfb to use tslib for the Samsung > display and touchscreen. Using OE, I built a directfb version with tslib > support ( added --with-inputdrivers=tslib to EXTRA_OECONF) and it all > installed just fine. Unfortunately I did not see any input support show > up in the directfb debug output messages. Here is what I am getting: > > =======================| DirectFB 1.1.0 |======================= > (c) 2001-2007 The DirectFB Organization (directfb.org) > (c) 2000-2004 Convergence (integrated media) GmbH > ------------------------------------------------------------ > > (*) DirectFB/Core: Single Application Core. (2008-08-19 19:49) > (*) Direct/Thread: Running 'VT Switcher' (CRITICAL, 812)... > (!) Direct/Modules: Could not open module directory > `/usr/lib/directfb-1.1-0/gfxdrivers'! > --> No such file or directory > (*) DirectFB/Graphics: Generic Software Rasterizer 0.6 (directfb.org) > (*) DirectFB/Core/WM: Default 0.3 (directfb.org) > (*) FBDev/Mode: Testing 480x272 RGB16 > (*) FBDev/Mode: Preparing switch to 480x272 RGB16 > (*) FBDev/Mode: Testing 480x272 RGB16 > (*) FBDev/Mode: Preparing switch to 480x272 RGB16 > > I did set up the TSLIB variables and tslib itself seems to be working > just fine. I am able to run the calibrate and test programs. > > Using OE version 318. > > Anyone able to get it to play or am I missing something key? > > Thanks > Mark > > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's challenge > Build the coolest Linux based applications with Moblin SDK & win great prizes > Grand prize is a trip for two to an Open Source event anywhere in the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > > Well I have narrowed down the problem a bit. It seems that the OE recipe for building the Directfb with Tslib is not setting up the correct search criteria for finding the Tslib when Automake runs. Here is the error message snipped from log.do_configure: checking pkg-config is at least version 0.9.0... yes checking for TSLIB... no configure: WARNING: *** no tslib -- tslib driver will not be built. configure: creating ./config.status config.status: creating directfb-config config.status: creating directfb.pc config.status: creating directfb-internal.pc Here is the reciepe for building Directfb. DESCRIPTION = "DirectFB is a thin library that provides developers \ with hardware graphics acceleration, input device handling and \ abstraction, an integrated windowing system with support for \ translucent windows and multiple display layers on top of the \ Linux framebuffer device." SECTION = "libs" LICENSE = "LGPL" HOMEPAGE = "http://directfb.org" DEPENDS = "jpeg libpng freetype zlib tslib" PR = "r3" RV = "1.1-0" SRC_URI = "http://www.directfb.org/download/DirectFB/DirectFB-${PV}.tar.gz \ file://fix-pkgconfig-cflags.patch;patch=1 \ file://fix-font-missing-char.patch;patch=1 \ file://getpagesize.patch;patch=1 \ file://fix-includes.patch;patch=1 \ file://mkdfiff.patch;patch=1" S = "${WORKDIR}/DirectFB-${PV}" LDFLAGS_append =" -lts -lm" inherit autotools pkgconfig EXTRA_OECONF = "--with-gfxdrivers=none \ --enable-libmpeg3=no \ --enable-freetype=yes \ --enable-sdl=no \ --enable-vnc=no \ --disable-x11 \ --with-inputdrivers=tslib \ " do_stage() { autotools_stage_all } do_install() { oe_runmake 'DESTDIR=${D}' install } PACKAGES_DYNAMIC = "directfb-inputdrivers-*" #python populate_packages_prepend () { # import os.path # inputdrivers_libdir = bb.data.expand('${libdir}/directfb-${RV}/inputdrivers', d) # do_split_packages(d, inputdrivers_libdir, '*.so$', 'directfb-inputdrivers-%s', 'Directfb plugin for %s') #} FILES_directfb-dbg_append = " ${libdir}/directfb-${RV}/*/*/.debug/*.so \ ${libdir}/directfb-${RV}/*/.debug/*.so \ " FILES_directfb-dev_append = " ${libdir}/directfb-${RV}/systems/*.la \ ${libdir}/directfb-${RV}/inputdrivers/*.la \ ${libdir}/directfb-${RV}/interfaces/*/*.la \ ${libdir}/directfb-${RV}/wm/*.la \ " FILES_directfb_append = " ${libdir}/directfb-${RV}/systems/*.so \ # ${libdir}/directfb-${RV}/inputdrivers/*.so \ # ${libdir}/directfb-${RV}/interfaces/*/*.so \ ${libdir}/directfb-${RV}/wm/*.so \ ${datadir}/directfb-1.1.0 \ " I noticed that the section python populate_packages_prepend is commented out. I tried uncommenting ,but I got several error messages to the effect dir or file not found. I guess there is a good reason for it being commented out. Does anyone know the proper way to tell the Automake process the library path for a bitbake recipe? Sorry for the long post Mark |
From: Darren M <d_m...@op...> - 2008-08-30 07:47:19
|
Hi Mark, I've just been through similar problems. If you're still having problems have a look at this thread on DirectFB Users. http://www.nabble.com/forum/ViewPost.jtp?post=19221341&framed=y Darren Mark Barton-2 wrote: > > Mark Barton wrote: >> Hi All, >> I have some trouble getting directfb to use tslib for the Samsung >> display and touchscreen. Using OE, I built a directfb version with tslib >> support ( added --with-inputdrivers=tslib to EXTRA_OECONF) and it all >> installed just fine. Unfortunately I did not see any input support show >> up in the directfb debug output messages. Here is what I am getting: >> > > -- View this message in context: http://www.nabble.com/problem-with-directfb-and-tslib-tp19069489p19231222.html Sent from the Gumstix mailing list archive at Nabble.com. |
From: Mark B. <ma...@at...> - 2008-08-30 15:14:36
|
Darren M wrote: > Hi Mark, > I've just been through similar problems. If you're still having problems > have a look at this thread on DirectFB Users. > http://www.nabble.com/forum/ViewPost.jtp?post=19221341&framed=y > Darren > > > Mark Barton-2 wrote: > >> Mark Barton wrote: >> >>> Hi All, >>> I have some trouble getting directfb to use tslib for the Samsung >>> display and touchscreen. Using OE, I built a directfb version with tslib >>> support ( added --with-inputdrivers=tslib to EXTRA_OECONF) and it all >>> installed just fine. Unfortunately I did not see any input support show >>> up in the directfb debug output messages. Here is what I am getting: >>> >>> >> > > Thanks Darren, I'll take a look at it again soon. Unfortunately my client who originally specified SDL has decided to go down a different path. I an still interested in getting it working regardless. Mark |