[Buildroot] Qt mouse, keyboard, touchscreen

[Buildroot] Qt mouse, keyboard, touchscreen

[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.
?
Regards
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20121124/9db2df41/attachment.html>

[Buildroot] Qt mouse, keyboard, touchscreen

[Stephan Hoffmann]

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
> 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/20121124/f72e0df2/attachment.html>

[Buildroot] Qt mouse, keyboard, touchscreen

[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!
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 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   
_______________________________________________
buildroot mailing list
buildroot at busybox.net
http://lists.busybox.net/mailman/listinfo/buildroot
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20121125/ef2c18dc/attachment.html>

[Buildroot] Qt mouse, keyboard, touchscreen

[Stephan Hoffmann]

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>

[Buildroot] Qt mouse, keyboard, touchscreen

[Stephan Hoffmann]

Am 26.11.2012 09:09, schrieb Zoran Djordjevic:
> I didn't go that way - with make clean (rather tried with deleting
> .stamp files).
> It is because building process is so lengthy. But I will probably try
> that.
My experience is that often "make xxx-reconfigure" is enough. But when
there are strange error messages "make clean" often is worth the waiting.
> What  else is left for me to do.
>  
> Regards
>
> *From:* Stephan Hoffmann <sho@relinux.de>
> *To:* Zoran Djordjevic <djdjdjole@yahoo.com>
> *Sent:* Monday, November 26, 2012 8:58 AM
> *Subject:* Re: [Buildroot] Qt mouse, keyboard, touchscreen
>
> 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 mailto:sho at relinux.de
>> *To:* buildroot at busybox.net <mailto:buildroot@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
> http://www.relinux.de/     sho at reLinux.de <mailto:sho@reLinux.de>
>
>
>


-- 
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/c957e2d8/attachment-0001.html>

[Buildroot] Qt mouse, keyboard, touchscreen

[Zoran Djordjevic]

I recompiled my RFS. This is what I checked in Buildroot menues:
for mouse: tslib, linux input, qvfb (what qvfb means ?)
for keyboard: linux input, qvfb
My /dev/input node has event0, event1, mouse0 and mice.
When I give: export QWS_MOUSE_PROTO=tslib:/dev/input/event0, 
touch screen works fine. However, tried different options for USB?mouse,
and neither one works (cat /dev/input/mouse0 or mice gives terminal "garbage").
Regarding keyboard, I gave: export QWS_KEYBOARD=linuxinput:/dev/input/event1
Keyboard (USB)?does work, but from that moment my terminal connected 
keyboard (via COM port) - doesn't work (Ctrl-C). When exiting application,
I can't give commands via terminal. Any help ?
?
Regards

 

________________________________
 From: Stephan Hoffmann <sho@relinux.de>
To: Zoran Djordjevic <djdjdjole@yahoo.com> 
Cc: buildroot at busybox.net 
Sent: Monday, November 26, 2012 9:17 AM
Subject: Re: [Buildroot] Qt mouse, keyboard, touchscreen
  

 
Am 26.11.2012 09:09, schrieb Zoran Djordjevic: 
I didn't go that way -?with make clean?(rather tried with deleting .stamp files). 
>It is because building process is so lengthy. But I will probably try that.  
My experience is that often "make xxx-reconfigure" is enough. But when there are strange error messages "make clean" often is worth the waiting.

What? else is left for me to do. 
>? 
>Regards 
>
> 
>From: Stephan Hoffmann mailto:sho at relinux.de
>To: Zoran Djordjevic mailto:djdjdjole at yahoo.com 
>Sent: Monday, November 26, 2012 8:58 AM
>Subject: Re: [Buildroot] Qt mouse, keyboard, touchscreen
>  
>
>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 mailto:sho at 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 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    
>>_______________________________________________
>>buildroot mailing list
>>buildroot at 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    
>
>    


-- 
reLinux     -    Stephan Hoffmann
Am Schmidtgrund 124    50765 K?ln
Tel. +49.221.95595-19    Fax: -64 http://www.relinux.de/ sho at reLinux.de   
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20121126/68a53a49/attachment.html>

[Buildroot] Qt mouse, keyboard, touchscreen

[Stephan Hoffmann]

Am 27.11.2012 08:46, schrieb Zoran Djordjevic:
> I recompiled my RFS. This is what I checked in Buildroot menues:
> for mouse: tslib, linux input, qvfb (what qvfb means ?)
> for keyboard: linux input, qvfb
> My /dev/input node has event0, event1, mouse0 and mice.
> When I give: export QWS_MOUSE_PROTO=tslib:/dev/input/event0,
> touch screen works fine. However, tried different options for USB mouse,
> and neither one works (cat /dev/input/mouse0 or mice gives terminal
> "garbage").
> Regarding keyboard, I gave: export
> QWS_KEYBOARD=linuxinput:/dev/input/event1
> Keyboard (USB) does work, but from that moment my terminal connected
> keyboard (via COM port) - doesn't work (Ctrl-C). When exiting application,
> I can't give commands via terminal. Any help ?
Sorry, but I do not have any idea. It seems odd that trying to use a USB
keyboard breaks the serial console.

Maybe someone else can give some advice.

Stephan
>  
> Regards
>
> *From:* Stephan Hoffmann <sho@relinux.de>
> *To:* Zoran Djordjevic <djdjdjole@yahoo.com>
> *Cc:* buildroot at busybox.net
> *Sent:* Monday, November 26, 2012 9:17 AM
> *Subject:* Re: [Buildroot] Qt mouse, keyboard, touchscreen
>
> Am 26.11.2012 09:09, schrieb Zoran Djordjevic:
>> I didn't go that way - with make clean (rather tried with deleting
>> .stamp files).
>> It is because building process is so lengthy. But I will probably try
>> that.
> My experience is that often "make xxx-reconfigure" is enough. But when
> there are strange error messages "make clean" often is worth the waiting.
>> What  else is left for me to do.
>>  
>> Regards
>>
>> *From:* Stephan Hoffmann mailto:sho at relinux.de
>> *To:* Zoran Djordjevic mailto:djdjdjole at yahoo.com
>> *Sent:* Monday, November 26, 2012 8:58 AM
>> *Subject:* Re: [Buildroot] Qt mouse, keyboard, touchscreen
>>
>> 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 mailto:sho at relinux.de
>>> *To:* buildroot at busybox.net <mailto:buildroot@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
>> http://www.relinux.de/     sho at reLinux.de <mailto:sho@reLinux.de>
>>
>>
>>
>
>
> -- 
> 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>
>
>
>


-- 
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/20121127/d0859568/attachment-0001.html>

[Buildroot] Qt mouse, keyboard, touchscreen

[Thomas Petazzoni]

Dear Zoran Djordjevic,

On Mon, 26 Nov 2012 23:46:15 -0800 (PST), Zoran Djordjevic wrote:

> My /dev/input node has event0, event1, mouse0 and mice.
> When I give: export QWS_MOUSE_PROTO=tslib:/dev/input/event0, 
> touch screen works fine. However, tried different options for
> USB?mouse, and neither one works (cat /dev/input/mouse0 or mice gives
> terminal "garbage"). Regarding keyboard, I gave: export
> QWS_KEYBOARD=linuxinput:/dev/input/event1 Keyboard (USB)?does work,
> but from that moment my terminal connected keyboard (via COM port) -
> doesn't work (Ctrl-C). When exiting application, I can't give
> commands via terminal. Any help ? 

Apply the attached patch to Qt.

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: qt-4.7.3-remove-ioctl.patch
Type: text/x-patch
Size: 721 bytes
Desc: not available
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20121127/37192ff9/attachment.bin>

[Buildroot] Qt mouse, keyboard, touchscreen

[Zoran Djordjevic]

I've tried patch, you submitted, and then make qt-reconfigure and
receive strange error about include folders. Same error I had 
earlier when trying with deleting stamp files (when added some
options regarding Qt in Buildroot's menuconfig), and in that case 
I had to do make clean all. But if I do so, now, I think I will loose my 
patched files (am I right ?)
What to do then ? 
?

________________________________
 From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: Zoran Djordjevic <djdjdjole@yahoo.com> 
Cc: Stephan Hoffmann <sho@relinux.de>; "buildroot at busybox.net" <buildroot@busybox.net> 
Sent: Tuesday, November 27, 2012 4:30 PM
Subject: Re: [Buildroot] Qt mouse, keyboard, touchscreen
  
Dear Zoran Djordjevic,

On Mon, 26 Nov 2012 23:46:15 -0800 (PST), Zoran Djordjevic wrote:

> My /dev/input node has event0, event1, mouse0 and mice.
> When I give: export QWS_MOUSE_PROTO=tslib:/dev/input/event0, 
> touch screen works fine. However, tried different options for
> USB?mouse, and neither one works (cat /dev/input/mouse0 or mice gives
> terminal "garbage"). Regarding keyboard, I gave: export
> QWS_KEYBOARD=linuxinput:/dev/input/event1 Keyboard (USB)?does work,
> but from that moment my terminal connected keyboard (via COM port) -
> doesn't work (Ctrl-C). When exiting application, I can't give
> commands via terminal. Any help ? 

Apply the attached patch to Qt.

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20121128/99be9bad/attachment.html>

[Buildroot] Qt mouse, keyboard, touchscreen

[Thomas Petazzoni]

Dear Zoran Djordjevic,

On Wed, 28 Nov 2012 03:36:44 -0800 (PST), Zoran Djordjevic wrote:
> I've tried patch, you submitted, and then make qt-reconfigure and

qt-reconfigure will not re-extract the source code and apply the
patches, so it is not appropriate. If you want to rebuild a package
from scratch, including extracting the package and applying the
patches, do:

	make qt-dirclean

> receive strange error about include folders. Same error I had 
> earlier when trying with deleting stamp files (when added some
> options regarding Qt in Buildroot's menuconfig), and in that case 
> I had to do make clean all. But if I do so, now, I think I will loose my 
> patched files (am I right ?)

If you made changes to output/build/<something>/, yes, you will loose
your changes. But you shouldn't be making any change in
output/build/<something>/

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

[Buildroot] Qt mouse, keyboard, touchscreen

[Zoran Djordjevic]

Probably, because of?being unfamiliar?with svn, I made
some mistake. I directly changed the source code, according
to patch file, you submitted (it is easy to understand the procedure)
, and then do qt-reconfigure.
Also, the only one file qkbdlinuxinput_qws.cpp, after building
root file system is at .../output/build... directory, so what file
should I change ?
If I made a mistake with such procedure, can you tell me
what is regular procedure ?
?
Regards


________________________________
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: Zoran Djordjevic <djdjdjole@yahoo.com> 
Cc: "buildroot at busybox.net" <buildroot@busybox.net> 
Sent: Wednesday, November 28, 2012 2:00 PM
Subject: Re: [Buildroot] Qt mouse, keyboard, touchscreen

Dear Zoran Djordjevic,

On Wed, 28 Nov 2012 03:36:44 -0800 (PST), Zoran Djordjevic wrote:
> I've tried patch, you submitted, and then make qt-reconfigure and

qt-reconfigure will not re-extract the source code and apply the
patches, so it is not appropriate. If you want to rebuild a package
from scratch, including extracting the package and applying the
patches, do:

??? make qt-dirclean

> receive strange error about include folders. Same error I had 
> earlier when trying with deleting stamp files (when added some
> options regarding Qt in Buildroot's menuconfig), and in that case 
> I had to do make clean all. But if I do so, now, I think I will loose my 
> patched files (am I right ?)

If you made changes to output/build/<something>/, yes, you will loose
your changes. But you shouldn't be making any change in
output/build/<something>/

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20121128/b8a1b017/attachment.html>