* [Buildroot] Qt4 Application - Touch detection @ 2015-01-15 17:03 Santhosh Ramani 2015-01-15 17:13 ` Björn Kirchner 0 siblings, 1 reply; 16+ messages in thread From: Santhosh Ramani @ 2015-01-15 17:03 UTC (permalink / raw) To: buildroot Hello Everyone, I am having some problems with running a Qt4 application with the buildroot RFS. The application renders fine and the screen looks perfect but touch detection does not work consistently and also seems to be off. I have calibrated the touch with ts_calibrate and ts_test also works perfectly. However when I run my app, touch detection doesn't work properly. I have built my app in Qt 4.8.4 and used the libraries from the TI SDK. I have also copied all the relevant libraries to the RFS and I don't get any errors for library dependency. When I enable the mouse pointer to be displayed in my application, I can see that the pointer shows up in completely the wrong spot. But if I kill my application and start the ts_test it works perfectly; that is how I can know that the calibration is good. Can someone please point me in the right direction? Thank you for your help, it's much appreciated :) Regards Santhosh -- Greater the Difficulty....Sweeter is the Victory -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20150115/ee263cd8/attachment.html> ^ permalink raw reply [flat|nested] 16+ messages in thread
* [Buildroot] Qt4 Application - Touch detection 2015-01-15 17:03 [Buildroot] Qt4 Application - Touch detection Santhosh Ramani @ 2015-01-15 17:13 ` Björn Kirchner [not found] ` <CADKZYYKDoizsdEo28Ynwb=ndhJXmHW3Zoqx=aSpP-1BMnDYujw@mail.gmail.com> 0 siblings, 1 reply; 16+ messages in thread From: Björn Kirchner @ 2015-01-15 17:13 UTC (permalink / raw) To: buildroot Am Thu, 15 Jan 2015 11:03:38 -0600 schrieb Santhosh Ramani <srcoolz@gmail.com>: > Hello Everyone, > > I am having some problems with running a Qt4 application with the > buildroot RFS. The application renders fine and the screen looks > perfect but touch detection does not work consistently and also seems > to be off. > > I have calibrated the touch with ts_calibrate and ts_test also works > perfectly. However when I run my app, touch detection doesn't work > properly. I have built my app in Qt 4.8.4 and used the libraries from > the TI SDK. I have also copied all the relevant libraries to the RFS > and I don't get any errors for library dependency. > I used Qt 4.8.x on x86 with a touch screen. But I built it with buildroot and didn't copy it from a SDK. With that buildroot built Qt it worked very well. Two things for you to check: 1. Is environment variable TSLIB_TSDEVICE set to the correct input device found under /dev/input/eventX ? 2. Is environment variable QWS_MOUSE_PROTO set to "tslib:/dev/input/eventX" ? > When I enable the mouse pointer to be displayed in my application, I > can see that the pointer shows up in completely the wrong spot. But > if I kill my application and start the ts_test it works perfectly; > that is how I can know that the calibration is good. > > Can someone please point me in the right direction? Thank you for your > help, it's much appreciated :) > > Regards > > Santhosh > Regards Bj?rn ^ permalink raw reply [flat|nested] 16+ messages in thread
[parent not found: <CADKZYYKDoizsdEo28Ynwb=ndhJXmHW3Zoqx=aSpP-1BMnDYujw@mail.gmail.com>]
* [Buildroot] Fwd: Qt4 Application - Touch detection [not found] ` <CADKZYYKDoizsdEo28Ynwb=ndhJXmHW3Zoqx=aSpP-1BMnDYujw@mail.gmail.com> @ 2015-01-15 17:57 ` Santhosh Ramani 2015-01-15 19:06 ` Björn Kirchner 0 siblings, 1 reply; 16+ messages in thread From: Santhosh Ramani @ 2015-01-15 17:57 UTC (permalink / raw) To: buildroot Hello Bjorn, Thanks for the quick reply. 1. Is environment variable TSLIB_TSDEVICE set to the correct input > device found under /dev/input/eventX ? > 2. Is environment variable QWS_MOUSE_PROTO set to > "tslib:/dev/input/eventX" ? I do have a startup script where I export these variables prior to ts_calibrate. Do you want me to re-export them before running the application? I export the following variables: export TSLIB_TSDEVICE=/dev/input/event0 export TSLIB_TSEVENTTYPE=INPUT export TSLIB_CONFFILE=/etc/ts.conf export TSLIB_CALIBFILE=/etc/pointercal export QWS_MOUSE_PROTO="Tslib:/dev/input/event0" I do have a question - when I print the environment variables, these do not show up. I use the 'printenv' command, and these are not listed. Is that a problem? I used Qt 4.8.x on x86 with a touch screen. But I built it with > buildroot and didn't copy it from a SDK. With that buildroot built Qt > it worked very well. I will test this out and reply back to you. Thank you once again. Regards Santhosh -- Greater the Difficulty....Sweeter is the Victory -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20150115/7a28e6c2/attachment.html> ^ permalink raw reply [flat|nested] 16+ messages in thread
* [Buildroot] Fwd: Qt4 Application - Touch detection 2015-01-15 17:57 ` [Buildroot] Fwd: " Santhosh Ramani @ 2015-01-15 19:06 ` Björn Kirchner 2015-01-15 20:01 ` Santhosh Ramani 0 siblings, 1 reply; 16+ messages in thread From: Björn Kirchner @ 2015-01-15 19:06 UTC (permalink / raw) To: buildroot Am Thu, 15 Jan 2015 11:57:20 -0600 schrieb Santhosh Ramani <srcoolz@gmail.com>: > Hello Bjorn, > > Thanks for the quick reply. > > 1. Is environment variable TSLIB_TSDEVICE set to the correct input > > device found under /dev/input/eventX ? > > 2. Is environment variable QWS_MOUSE_PROTO set to > > "tslib:/dev/input/eventX" ? > > > I do have a startup script where I export these variables prior to > ts_calibrate. Do you want me to re-export them before running the > application? I export the following variables: > > export TSLIB_TSDEVICE=/dev/input/event0 > export TSLIB_TSEVENTTYPE=INPUT > export TSLIB_CONFFILE=/etc/ts.conf > export TSLIB_CALIBFILE=/etc/pointercal > export QWS_MOUSE_PROTO="Tslib:/dev/input/event0" > Does the capital 'T' in "Tslib" make any difference? I've only seen it written as 't', yet. Do you reboot between calibration and starting of your program? In my case the devices changed occasionally between reboots, so /dev/input/event0 was not always the correct device. > I do have a question - when I print the environment variables, these > do not show up. I use the 'printenv' command, and these are not > listed. Is that a problem? I'm not quite sure here. If you start a script which exports environment variables, I think those exportes variables only exist in this script and in its child processes. So, if you start ts_calibrate with a start script and after that your program from a differnt script or directly from your login shell, I suppose those variables aren't set anymore. Please try to export them either in a start script for your application or, as a quick test, in the shell you use to start your program. Just to make sure... > > > I used Qt 4.8.x on x86 with a touch screen. But I built it with > > buildroot and didn't copy it from a SDK. With that buildroot built > > Qt it worked very well. > > > I will test this out and reply back to you. > > Thank you once again. > Regards > > Santhosh > > > > > ^ permalink raw reply [flat|nested] 16+ messages in thread
* [Buildroot] Fwd: Qt4 Application - Touch detection 2015-01-15 19:06 ` Björn Kirchner @ 2015-01-15 20:01 ` Santhosh Ramani 2015-01-15 20:22 ` Björn Kirchner 0 siblings, 1 reply; 16+ messages in thread From: Santhosh Ramani @ 2015-01-15 20:01 UTC (permalink / raw) To: buildroot Hello Bjorn, Thanks once again for your reply. Does the capital 'T' in "Tslib" make any difference? I've only seen > it written as 't', yet. Do you reboot between calibration and starting > of your program? In my case the devices changed occasionally between > reboots, so /dev/input/event0 was not always the correct device. I tried with both options, but the results are the same. In my case, it's always /dev/input/event0 so I think I'm okay here. I'm not quite sure here. If you start a script which exports environment > variables, I think those exportes variables only exist in this script > and in its child processes. So, if you start ts_calibrate with a start > script and after that your program from a differnt script or directly > from your login shell, I suppose those variables aren't set anymore. > Please try to export them either in a start script for your application > or, as a quick test, in the shell you use to start your program. Just > to make sure... I tried exporting the variables from command line along with the scripts and also the method you suggested, but there was no change in operation. I was able to run the qt examples and once I exported the variables from command line those examples worked fine. I'm going to try to compile my Qt application with the library built by buildroot and see if that helps. Do you have any other suggestions? Thanks - Santhosh -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20150115/f6b45c3d/attachment.html> ^ permalink raw reply [flat|nested] 16+ messages in thread
* [Buildroot] Fwd: Qt4 Application - Touch detection 2015-01-15 20:01 ` Santhosh Ramani @ 2015-01-15 20:22 ` Björn Kirchner 2015-01-15 20:44 ` Santhosh Ramani 0 siblings, 1 reply; 16+ messages in thread From: Björn Kirchner @ 2015-01-15 20:22 UTC (permalink / raw) To: buildroot Am Thu, 15 Jan 2015 14:01:14 -0600 schrieb Santhosh Ramani <srcoolz@gmail.com>: > Hello Bjorn, > > Thanks once again for your reply. > > Does the capital 'T' in "Tslib" make any difference? I've only seen > > it written as 't', yet. Do you reboot between calibration and > > starting of your program? In my case the devices changed > > occasionally between reboots, so /dev/input/event0 was not always > > the correct device. > > > I tried with both options, but the results are the same. In my case, > it's always /dev/input/event0 so I think I'm okay here. > > I'm not quite sure here. If you start a script which exports > environment > > variables, I think those exportes variables only exist in this > > script and in its child processes. So, if you start ts_calibrate > > with a start script and after that your program from a differnt > > script or directly from your login shell, I suppose those variables > > aren't set anymore. Please try to export them either in a start > > script for your application or, as a quick test, in the shell you > > use to start your program. Just to make sure... > > > I tried exporting the variables from command line along with the > scripts and also the method you suggested, but there was no change in > operation. I was able to run the qt examples and once I exported the > variables from command line those examples worked fine. So, you did something like this? # export TSLIB_TSDEVICE=/dev/input/event0 # export QWS_MOUSE_PROTO="tslib:/dev/input/event0" # <qtExample> And there the touch screen worked correctly? And your program didn't? > > I'm going to try to compile my Qt application with the library built > by buildroot and see if that helps. Do you have any other suggestions? > > Thanks > > - Santhosh ^ permalink raw reply [flat|nested] 16+ messages in thread
* [Buildroot] Fwd: Qt4 Application - Touch detection 2015-01-15 20:22 ` Björn Kirchner @ 2015-01-15 20:44 ` Santhosh Ramani 2015-01-15 21:04 ` Charles Krinke 2015-01-16 5:49 ` bjoern at am-soft.de 0 siblings, 2 replies; 16+ messages in thread From: Santhosh Ramani @ 2015-01-15 20:44 UTC (permalink / raw) To: buildroot > > So, you did something like this? > # export TSLIB_TSDEVICE=/dev/input/event0 > # export QWS_MOUSE_PROTO="tslib:/dev/input/event0" > # <qtExample> > And there the touch screen worked correctly? And your program didn't? Yes that is correct. However, I still don't understand why export doesn't work within a script. I understood your explanation; the TI file system uses profile.d to export these variables again in bash. I will try doing that with profile file in etc to make it part of the startup routine. I'm going to try and compile my application with the Qt built by buildroot and I will reply back with my findings. Thanks once again for your patience and help. Regards Santhosh -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20150115/abc1e687/attachment.html> ^ permalink raw reply [flat|nested] 16+ messages in thread
* [Buildroot] Fwd: Qt4 Application - Touch detection 2015-01-15 20:44 ` Santhosh Ramani @ 2015-01-15 21:04 ` Charles Krinke 2015-01-15 22:09 ` Santhosh Ramani 2015-01-16 5:49 ` bjoern at am-soft.de 1 sibling, 1 reply; 16+ messages in thread From: Charles Krinke @ 2015-01-15 21:04 UTC (permalink / raw) To: buildroot On the invocation of the qt program, perhaps this argument might help -plugin Tslib:/dev/input/event0 On Thu, Jan 15, 2015 at 12:44 PM, Santhosh Ramani <srcoolz@gmail.com> wrote: > So, you did something like this? >> # export TSLIB_TSDEVICE=/dev/input/event0 >> # export QWS_MOUSE_PROTO="tslib:/dev/input/event0" >> # <qtExample> >> And there the touch screen worked correctly? And your program didn't? > > > Yes that is correct. However, I still don't understand why export doesn't > work within a script. I understood your explanation; the TI file system > uses profile.d to export these variables again in bash. I will try doing > that with profile file in etc to make it part of the startup routine. > > I'm going to try and compile my application with the Qt built by buildroot > and I will reply back with my findings. > > Thanks once again for your patience and help. > Regards > > Santhosh > > _______________________________________________ > buildroot mailing list > buildroot at busybox.net > http://lists.busybox.net/mailman/listinfo/buildroot > -- Charles Krinke -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20150115/e5a7ff6a/attachment.html> ^ permalink raw reply [flat|nested] 16+ messages in thread
* [Buildroot] Fwd: Qt4 Application - Touch detection 2015-01-15 21:04 ` Charles Krinke @ 2015-01-15 22:09 ` Santhosh Ramani 2015-01-15 22:27 ` Charles Krinke 2015-01-16 5:53 ` bjoern at am-soft.de 0 siblings, 2 replies; 16+ messages in thread From: Santhosh Ramani @ 2015-01-15 22:09 UTC (permalink / raw) To: buildroot > > On the invocation of the qt program, perhaps this argument might help > -plugin Tslib:/dev/input/event0 Hello Charles, Thanks for the suggestion, I tried it but there is still no difference. Additionally I added a mouse pointer to be visible in my application and I can see that the touchevent is picked up, just that it's completely off even if I calibrate it every time at power up. Regards Santhosh -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20150115/a9315c57/attachment.html> ^ permalink raw reply [flat|nested] 16+ messages in thread
* [Buildroot] Fwd: Qt4 Application - Touch detection 2015-01-15 22:09 ` Santhosh Ramani @ 2015-01-15 22:27 ` Charles Krinke 2015-01-15 23:33 ` Santhosh Ramani 2015-01-16 5:53 ` bjoern at am-soft.de 1 sibling, 1 reply; 16+ messages in thread From: Charles Krinke @ 2015-01-15 22:27 UTC (permalink / raw) To: buildroot Interesting. I have an AM3517 and did all the things you did and it worked. The -plugin was one of the last. It feels like this is some some of Qt compile and invocation issue, not necessarily a root filesystem issue. On Thu, Jan 15, 2015 at 2:09 PM, Santhosh Ramani <srcoolz@gmail.com> wrote: > On the invocation of the qt program, perhaps this argument might help >> -plugin Tslib:/dev/input/event0 > > > Hello Charles, > > Thanks for the suggestion, I tried it but there is still no difference. > Additionally I added a mouse pointer to be visible in my application and I > can see that the touchevent is picked up, just that it's completely off > even if I calibrate it every time at power up. > > Regards > > Santhosh > > -- Charles Krinke -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20150115/0d88fea8/attachment.html> ^ permalink raw reply [flat|nested] 16+ messages in thread
* [Buildroot] Fwd: Qt4 Application - Touch detection 2015-01-15 22:27 ` Charles Krinke @ 2015-01-15 23:33 ` Santhosh Ramani 0 siblings, 0 replies; 16+ messages in thread From: Santhosh Ramani @ 2015-01-15 23:33 UTC (permalink / raw) To: buildroot Thanks for the help Charles. On 15 January 2015 at 16:27, Charles Krinke <charles.krinke@gmail.com> wrote: > Interesting. I have an AM3517 and did all the things you did and it > worked. The -plugin was one of the last. It feels like this is some some of > Qt compile and invocation issue, not necessarily a root filesystem issue. > > On Thu, Jan 15, 2015 at 2:09 PM, Santhosh Ramani <srcoolz@gmail.com> > wrote: > >> On the invocation of the qt program, perhaps this argument might help >>> -plugin Tslib:/dev/input/event0 >> >> >> Hello Charles, >> >> Thanks for the suggestion, I tried it but there is still no difference. >> Additionally I added a mouse pointer to be visible in my application and I >> can see that the touchevent is picked up, just that it's completely off >> even if I calibrate it every time at power up. >> >> Regards >> >> Santhosh >> >> > > > -- > Charles Krinke > > -- Greater the Difficulty....Sweeter is the Victory -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20150115/1310fae2/attachment.html> ^ permalink raw reply [flat|nested] 16+ messages in thread
* [Buildroot] Fwd: Qt4 Application - Touch detection 2015-01-15 22:09 ` Santhosh Ramani 2015-01-15 22:27 ` Charles Krinke @ 2015-01-16 5:53 ` bjoern at am-soft.de 2015-01-16 17:26 ` Santhosh Ramani 1 sibling, 1 reply; 16+ messages in thread From: bjoern at am-soft.de @ 2015-01-16 5:53 UTC (permalink / raw) To: buildroot >> >> On the invocation of the qt program, perhaps this argument might help >> -plugin Tslib:/dev/input/event0 > > > Hello Charles, > > Thanks for the suggestion, I tried it but there is still no difference. > Additionally I added a mouse pointer to be visible in my application and I > can see that the touchevent is picked up, just that it's completely off > even if I calibrate it every time at power up. > Just a thought: Does your program (or better, the user who starts it) sufficent rights to access the calibration file? Do the Qt libraries load additional external libs at runtime? Or try to do so and fail (for example: tslib components)? Maybe they fall back in this case to a "wrong" input method? > Regards > > Santhosh > ^ permalink raw reply [flat|nested] 16+ messages in thread
* [Buildroot] Fwd: Qt4 Application - Touch detection 2015-01-16 5:53 ` bjoern at am-soft.de @ 2015-01-16 17:26 ` Santhosh Ramani 2015-01-16 18:10 ` Charles Krinke 0 siblings, 1 reply; 16+ messages in thread From: Santhosh Ramani @ 2015-01-16 17:26 UTC (permalink / raw) To: buildroot Hello Bjorn, Thank you for the detailed explanation of the environmental variables - it was really helpful. I've made sure that my startup scripts export all the necessary variables. Additionally I have also added it to my profile.d so that in case I kill the app and restart it, it can have access to those variables. I hope this approach is okay? My program is launched as root and I have only 1 user. I also looked at permissions for the /etc/pointercal - it seems fine to me. It has read permissions for all levels and rw for root. My colleague is gonna build the application using Qt built from buildroot and I'll post the results here once we run the application on our board. Thanks once again for your time and patience. Regards Santhosh On 15 January 2015 at 23:53, <bjoern@am-soft.de> wrote: > >> > >> On the invocation of the qt program, perhaps this argument might help > >> -plugin Tslib:/dev/input/event0 > > > > > > Hello Charles, > > > > Thanks for the suggestion, I tried it but there is still no difference. > > Additionally I added a mouse pointer to be visible in my application and > I > > can see that the touchevent is picked up, just that it's completely off > > even if I calibrate it every time at power up. > > > > Just a thought: Does your program (or better, the user who starts it) > sufficent rights to access the calibration file? > Do the Qt libraries load additional external libs at runtime? Or try to > do so and fail (for example: tslib components)? Maybe they fall back in > this case to a "wrong" input method? > > > Regards > > > > Santhosh > > > > > -- Greater the Difficulty....Sweeter is the Victory -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20150116/02b94042/attachment.html> ^ permalink raw reply [flat|nested] 16+ messages in thread
* [Buildroot] Fwd: Qt4 Application - Touch detection 2015-01-16 17:26 ` Santhosh Ramani @ 2015-01-16 18:10 ` Charles Krinke 2015-02-01 1:33 ` Santhosh Ramani 0 siblings, 1 reply; 16+ messages in thread From: Charles Krinke @ 2015-01-16 18:10 UTC (permalink / raw) To: buildroot Hang on a minute, Santhosh. You just said something that clicked. I "always" use Qt applications built only on buildroot for running on a buildroot generated filesystem with the Qt libraries. I cannot imagine cross-library stuff working properly, regardless of what the Qt folks say. The Qt developers I support grumbled and wanted to use windows and linux PC Qt, but I set them up with the tools in buildroot that were used to compile the libraries to ensure things worked properly. On Fri, Jan 16, 2015 at 9:26 AM, Santhosh Ramani <srcoolz@gmail.com> wrote: > Hello Bjorn, > > Thank you for the detailed explanation of the environmental variables - it > was really helpful. I've made sure that my startup scripts export all the > necessary variables. Additionally I have also added it to my profile.d so > that in case I kill the app and restart it, it can have access to those > variables. I hope this approach is okay? > > My program is launched as root and I have only 1 user. I also looked at > permissions for the /etc/pointercal - it seems fine to me. It has read > permissions for all levels and rw for root. My colleague is gonna build the > application using Qt built from buildroot and I'll post the results here > once we run the application on our board. > > Thanks once again for your time and patience. > Regards > > Santhosh > > > > On 15 January 2015 at 23:53, <bjoern@am-soft.de> wrote: > >> >> >> >> On the invocation of the qt program, perhaps this argument might help >> >> -plugin Tslib:/dev/input/event0 >> > >> > >> > Hello Charles, >> > >> > Thanks for the suggestion, I tried it but there is still no difference. >> > Additionally I added a mouse pointer to be visible in my application >> and I >> > can see that the touchevent is picked up, just that it's completely off >> > even if I calibrate it every time at power up. >> > >> >> Just a thought: Does your program (or better, the user who starts it) >> sufficent rights to access the calibration file? >> Do the Qt libraries load additional external libs at runtime? Or try to >> do so and fail (for example: tslib components)? Maybe they fall back in >> this case to a "wrong" input method? >> >> > Regards >> > >> > Santhosh >> > >> >> >> > > > -- > Greater the Difficulty....Sweeter is the Victory > -- Charles Krinke -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20150116/cf83c7cf/attachment.html> ^ permalink raw reply [flat|nested] 16+ messages in thread
* [Buildroot] Fwd: Qt4 Application - Touch detection 2015-01-16 18:10 ` Charles Krinke @ 2015-02-01 1:33 ` Santhosh Ramani 0 siblings, 0 replies; 16+ messages in thread From: Santhosh Ramani @ 2015-02-01 1:33 UTC (permalink / raw) To: buildroot Hello Charles, We actually got it to work fine. Here is what we had to do to make it work: 1. Standard settings in buildroot, nothing fancy, nothing out of the ordinary. Using Qt 4 rather than Qt 5 - tslib and usb mouse input enabled. 2. Build Qt - the same version as what buildroot downloads. 3. Build Tslib - the same version as what buildroot downloads. 4. Build the application against the libraries from the build Qt and Tslib. Once these are done, the application works fine. So I guess it was more to do with making sure the application is built with the same Qt version and Tslib version as what is downloaded and installed by buildroot. Thanks a lot guys for taking the time and replying to my questions. Thank you for your patience. Regards Santhosh On 16 January 2015 at 12:10, Charles Krinke <charles.krinke@gmail.com> wrote: > Hang on a minute, Santhosh. You just said something that clicked. I > "always" use Qt applications built only on buildroot for running on a > buildroot generated filesystem with the Qt libraries. I cannot imagine > cross-library stuff working properly, regardless of what the Qt folks say. > > The Qt developers I support grumbled and wanted to use windows and linux > PC Qt, but I set them up with the tools in buildroot that were used to > compile the libraries to ensure things worked properly. > > On Fri, Jan 16, 2015 at 9:26 AM, Santhosh Ramani <srcoolz@gmail.com> > wrote: > >> Hello Bjorn, >> >> Thank you for the detailed explanation of the environmental variables - >> it was really helpful. I've made sure that my startup scripts export all >> the necessary variables. Additionally I have also added it to my profile.d >> so that in case I kill the app and restart it, it can have access to those >> variables. I hope this approach is okay? >> >> My program is launched as root and I have only 1 user. I also looked at >> permissions for the /etc/pointercal - it seems fine to me. It has read >> permissions for all levels and rw for root. My colleague is gonna build the >> application using Qt built from buildroot and I'll post the results here >> once we run the application on our board. >> >> Thanks once again for your time and patience. >> Regards >> >> Santhosh >> >> >> >> On 15 January 2015 at 23:53, <bjoern@am-soft.de> wrote: >> >>> >> >>> >> On the invocation of the qt program, perhaps this argument might help >>> >> -plugin Tslib:/dev/input/event0 >>> > >>> > >>> > Hello Charles, >>> > >>> > Thanks for the suggestion, I tried it but there is still no difference. >>> > Additionally I added a mouse pointer to be visible in my application >>> and I >>> > can see that the touchevent is picked up, just that it's completely off >>> > even if I calibrate it every time at power up. >>> > >>> >>> Just a thought: Does your program (or better, the user who starts it) >>> sufficent rights to access the calibration file? >>> Do the Qt libraries load additional external libs at runtime? Or try to >>> do so and fail (for example: tslib components)? Maybe they fall back in >>> this case to a "wrong" input method? >>> >>> > Regards >>> > >>> > Santhosh >>> > >>> >>> >>> >> >> >> -- >> Greater the Difficulty....Sweeter is the Victory >> > > > > -- > Charles Krinke > > -- Greater the Difficulty....Sweeter is the Victory -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20150131/0811fba6/attachment.html> ^ permalink raw reply [flat|nested] 16+ messages in thread
* [Buildroot] Fwd: Qt4 Application - Touch detection 2015-01-15 20:44 ` Santhosh Ramani 2015-01-15 21:04 ` Charles Krinke @ 2015-01-16 5:49 ` bjoern at am-soft.de 1 sibling, 0 replies; 16+ messages in thread From: bjoern at am-soft.de @ 2015-01-16 5:49 UTC (permalink / raw) To: buildroot >> >> So, you did something like this? >> # export TSLIB_TSDEVICE=/dev/input/event0 >> # export QWS_MOUSE_PROTO="tslib:/dev/input/event0" >> # <qtExample> >> And there the touch screen worked correctly? And your program didn't? > > > Yes that is correct. However, I still don't understand why export doesn't > work within a script. I understood your explanation; the TI file system > uses profile.d to export these variables again in bash. I will try doing > that with profile file in etc to make it part of the startup routine. > Imagine the processes on a linux system as a tree. For example: /sbin/init | | A | +--> B | | | | | C | D If you export a variable in process B this variable will be also available in process C. But B cannot change the environment of process A. Therefore this environment variable exported by B will not be available in process D. Does profile.d change non-login environments? If your program starts via a service at boot time I'm not sure if it gets an environment set up by the files in profile.d. I used the pragmatic approach and used start scripts for my programs that need specific environment variables set. > I'm going to try and compile my application with the Qt built by buildroot > and I will reply back with my findings. > > Thanks once again for your patience and help. > Regards > > Santhosh > ^ permalink raw reply [flat|nested] 16+ messages in thread
end of thread, other threads:[~2015-02-01 1:33 UTC | newest]
Thread overview: 16+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2015-01-15 17:03 [Buildroot] Qt4 Application - Touch detection Santhosh Ramani
2015-01-15 17:13 ` Björn Kirchner
[not found] ` <CADKZYYKDoizsdEo28Ynwb=ndhJXmHW3Zoqx=aSpP-1BMnDYujw@mail.gmail.com>
2015-01-15 17:57 ` [Buildroot] Fwd: " Santhosh Ramani
2015-01-15 19:06 ` Björn Kirchner
2015-01-15 20:01 ` Santhosh Ramani
2015-01-15 20:22 ` Björn Kirchner
2015-01-15 20:44 ` Santhosh Ramani
2015-01-15 21:04 ` Charles Krinke
2015-01-15 22:09 ` Santhosh Ramani
2015-01-15 22:27 ` Charles Krinke
2015-01-15 23:33 ` Santhosh Ramani
2015-01-16 5:53 ` bjoern at am-soft.de
2015-01-16 17:26 ` Santhosh Ramani
2015-01-16 18:10 ` Charles Krinke
2015-02-01 1:33 ` Santhosh Ramani
2015-01-16 5:49 ` bjoern at am-soft.de
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.