Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Stephan Hoffmann <sho@relinux.de>
To: buildroot@busybox.net
Subject: [Buildroot] Qt mouse, keyboard, touchscreen
Date: Mon, 26 Nov 2012 09:00:44 +0100	[thread overview]
Message-ID: <50B321AC.9090806@relinux.de> (raw)
In-Reply-To: <1353916198.97471.YahooMailNeo@web164601.mail.gq1.yahoo.com>

Am 26.11.2012 08:49, schrieb Zoran Djordjevic:
> OK - now I checked few options regarding Qt drivers in Buildroot
> menu and try rebuilding, but got error:
> The tslib functionality test failed!
Did you try "make clean"?
> You might need to modify the indluce and library search paths by editing
> QMAKE_INCDIR and QMAKE_LIBDIR in ....... (name of the config folder).
> I don't see either of those ones in qmake.conf in folder quoted, and also
> if I add them, don't know what to quote ?
>  
> Regards
>  
> *From:* Stephan Hoffmann <sho@relinux.de>
> *To:* buildroot at busybox.net
> *Sent:* Saturday, November 24, 2012 10:51 AM
> *Subject:* Re: [Buildroot] Qt mouse, keyboard, touchscreen
>
> Am 24.11.2012 10:19, schrieb Zoran Djordjevic:
>> Thanks to helpful information you provided, I managed to built
>> simple Qt application on my ARM board and it works - meaning
>> I got some window and some simple effect inside. I am using
>> framebuffer so started program with -qws option.
>> However mouse, keyboard and touchscreen are dead. In fact they
>> are probably visible by kernel (ts_calibrate and ts_test for example,
>> works OK and cat /dev/input/event0 shows "usuall" garbage on
>> terminal) however I don't know how to start them to work with Qt.
>> I successfully started them earlier while using TinyX and GTK, by
>> simply quoting them with xinit command parameters.
>> But don't know how to do the same with Qt.
> Hi,
>
> there are two things to consider:
>
> 1. Check if there are drivers enabled in buildroot config. The default
> configuration does not include any drivers. I stepped in this trap
> when I started to use QT.
>
> BTW: Shouldn't we change this to some useful default?
>
> 2. QT needs environment variables to configure input devices.
>
> http://doc.qt.digia.com/4.7/qt-embedded-envvars.html
>
> Hope this helps
>
> Stephan
>
>>  
>> Regards
>>
>>
>> _______________________________________________
>> buildroot mailing list
>> buildroot at busybox.net <mailto:buildroot@busybox.net>
>> http://lists.busybox.net/mailman/listinfo/buildroot
>
>
> -- 
> reLinux     -    Stephan Hoffmann
> Am Schmidtgrund 124    50765 K?ln
> Tel. +49.221.95595-19    Fax: -64
> http://www.relinux.de/     sho at reLinux.de <mailto:sho@reLinux.de>
>
>
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net <mailto:buildroot@busybox.net>
> http://lists.busybox.net/mailman/listinfo/buildroot
>


-- 
reLinux     -    Stephan Hoffmann
Am Schmidtgrund 124    50765 K?ln
Tel. +49.221.95595-19    Fax: -64
www.reLinux.de     sho at reLinux.de

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20121126/93241c04/attachment.html>

  reply	other threads:[~2012-11-26  8:00 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-24  9:19 [Buildroot] Qt mouse, keyboard, touchscreen Zoran Djordjevic
2012-11-24  9:51 ` Stephan Hoffmann
2012-11-26  7:49   ` Zoran Djordjevic
2012-11-26  8:00     ` Stephan Hoffmann [this message]
     [not found]     ` <50B3210E.2010806@relinux.de>
     [not found]       ` <1353917395.39625.YahooMailNeo@web164603.mail.gq1.yahoo.com>
2012-11-26  8:17         ` Stephan Hoffmann
2012-11-27  7:46           ` Zoran Djordjevic
2012-11-27 15:27             ` Stephan Hoffmann
2012-11-27 15:30             ` Thomas Petazzoni
2012-11-28 11:36               ` Zoran Djordjevic
2012-11-28 13:00                 ` Thomas Petazzoni
2012-11-28 17:11                   ` Zoran Djordjevic

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=50B321AC.9090806@relinux.de \
    --to=sho@relinux.de \
    --cc=buildroot@busybox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox