Qtopia-interest Archive, March 2008
Re: RE : RE : No output on framebuffer
Message 1 in thread
Hi Guillaume,
yes, I'm using qmake from qtopia and running make actually uses
arm-linux-gxx, building a working arm executable.
I've also connected a slot to the button's click() signal, just to cout
something to stdout, and even if I cannot see the button (as
I've mentioned) I can click it and see output on the console.
On a side note: when I move the cursor on the button, it fades
away and I cannot see the cursor too!
This, to me, means that I've got only problems in painting widgets
on linuxfb. The same program with standard qt (on my X11 linuxbox)
works fine.
I will try, as you suggest, using qtopia-4.3.4, but I think
the problem is actually somewhere else in the cross-compilation of qtopia
and/or in the toolchain I'm using.
I've seen in the list's archive that other people had the same
issue, but no one mentions a solution.
I will let you and the list know if I make any improvement.
Giorgio
>
> This code is ok for me...
>
> How do you compile it ?
>
> I suppose that you did like this :
> qmake -project
> qmake
> make
>
> with the qmake of qtopia (for cross compile)
>
> I tested this code on the board AT91SAM9261-EK (arm based) and on my desktop
> computer and it is working well (see the shot in attachment)
>
> Maybe the Qtopia libs are not installed correctly... or try the latest
> release of qtopia core. I run qtopia-core-opensource-src-4.3.4 on my board.
>
>
> Cheers,
>
> Guillaume
>
>
> -------- Message d'origine--------
> De: Giorgio Cardarelli [mailto:giorgio.cardarelli@xxxxxxxxxxx]
> Date: mer. 05/03/2008 09:10
> À: GARDET Guillaume; qtopia-interest@xxxxxxxxxxxxx
> Objet : Re: RE : No output on framebuffer
>
> Hello Guillaume,
> thanks for your quick reply. Here is the code.
>
> #include <QApplication>
> #include <QPushButton>
>
> int main(int argc, char *argv[]){
> QApplication app(argc, argv);
> QPushButton myWidget("prova");
> myWidget.show();
>
> return app.exec();
> }
>
> Really looking forward to hearing from your,
> thanks again,
>
> Giorgio
>
>
> >
> > Hello !
> >
> > It is maybe an "error" in your code... Could you send your code by mail ?
> I
> > (we) could test it and maybe find something ...
> >
> > Cheers,
> >
> > Guillaume
> >
> >
> >
> > -------- Message d'origine--------
> > De: Giorgio Cardarelli [mailto:giorgio.cardarelli@xxxxxxxxxxx]
> > Date: mar. 04/03/2008 16:36
> > À: qtopia-interest@xxxxxxxxxxxxx
> > Objet : No output on framebuffer
> >
> > Hello list,
> >
> > I've prepared a small application with a single QPushButton that
> > does nothing. I can compile the program with no errors, but
> > when I run it (./qt-test -qws) only the green "desktop" background
> > and the mouse cursor is displayed, while the button is not painted.
> > It seems like I can actually see what lies "under" the qtopia
> > application (in my case the linux console from where I started my
> > test app).
> >
> > I can give some further informations: I'm using an ARM PXA320 cpu,
> > qtopia-core-opensource-src-4.3.2, cross-compiling everything with
> > an arm-linux-gxx tested toolchain using no particular compiling
> > flags. I'm working with a linuxfb device, and the test program provided
> > with qtopia (examples/qtopiacore/framebuffer) works perfectly with
> > both 8bpp and 16bpp.
> >
> > Where am I wrong? Can anybody help me?
> >
> > Many thanks,
> > Giorgio
> >
> > --
> > To unsubscribe - send "unsubscribe" in the subject to
> > qtopia-interest-request@xxxxxxxxxxxxx
> >
> >
> >
> >
>
>
>
>
--
[ signature omitted ]
Message 2 in thread
hi !
I am using the buildroot cross-compilation toolchain and qtopia-core-opensource-src-4.3.4
If it is not working with the 4.3.4 maybe try the buildroot cross-compilation toolchain.
Let us know if any improvement are made !
Cheers,
Guillaume
-------- Message d'origine--------
De: Giorgio Cardarelli [mailto:giorgio.cardarelli@xxxxxxxxxxx]
Date: mer. 05/03/2008 10:49
À: GARDET Guillaume; qtopia-interest@xxxxxxxxxxxxx
Objet : Re: RE : RE : No output on framebuffer
Hi Guillaume,
yes, I'm using qmake from qtopia and running make actually uses
arm-linux-gxx, building a working arm executable.
I've also connected a slot to the button's click() signal, just to cout
something to stdout, and even if I cannot see the button (as
I've mentioned) I can click it and see output on the console.
On a side note: when I move the cursor on the button, it fades
away and I cannot see the cursor too!
This, to me, means that I've got only problems in painting widgets
on linuxfb. The same program with standard qt (on my X11 linuxbox)
works fine.
I will try, as you suggest, using qtopia-4.3.4, but I think
the problem is actually somewhere else in the cross-compilation of qtopia
and/or in the toolchain I'm using.
I've seen in the list's archive that other people had the same
issue, but no one mentions a solution.
I will let you and the list know if I make any improvement.
Giorgio
>
> This code is ok for me...
>
> How do you compile it ?
>
> I suppose that you did like this :
> qmake -project
> qmake
> make
>
> with the qmake of qtopia (for cross compile)
>
> I tested this code on the board AT91SAM9261-EK (arm based) and on my desktop
> computer and it is working well (see the shot in attachment)
>
> Maybe the Qtopia libs are not installed correctly... or try the latest
> release of qtopia core. I run qtopia-core-opensource-src-4.3.4 on my board.
>
>
> Cheers,
>
> Guillaume
>
>
> -------- Message d'origine--------
> De: Giorgio Cardarelli [mailto:giorgio.cardarelli@xxxxxxxxxxx]
> Date: mer. 05/03/2008 09:10
> À: GARDET Guillaume; qtopia-interest@xxxxxxxxxxxxx
> Objet : Re: RE : No output on framebuffer
>
> Hello Guillaume,
> thanks for your quick reply. Here is the code.
>
> #include <QApplication>
> #include <QPushButton>
>
> int main(int argc, char *argv[]){
> QApplication app(argc, argv);
> QPushButton myWidget("prova");
> myWidget.show();
>
> return app.exec();
> }
>
> Really looking forward to hearing from your,
> thanks again,
>
> Giorgio
>
>
> >
> > Hello !
> >
> > It is maybe an "error" in your code... Could you send your code by mail ?
> I
> > (we) could test it and maybe find something ...
> >
> > Cheers,
> >
> > Guillaume
> >
> >
> >
> > -------- Message d'origine--------
> > De: Giorgio Cardarelli [mailto:giorgio.cardarelli@xxxxxxxxxxx]
> > Date: mar. 04/03/2008 16:36
> > À: qtopia-interest@xxxxxxxxxxxxx
> > Objet : No output on framebuffer
> >
> > Hello list,
> >
> > I've prepared a small application with a single QPushButton that
> > does nothing. I can compile the program with no errors, but
> > when I run it (./qt-test -qws) only the green "desktop" background
> > and the mouse cursor is displayed, while the button is not painted.
> > It seems like I can actually see what lies "under" the qtopia
> > application (in my case the linux console from where I started my
> > test app).
> >
> > I can give some further informations: I'm using an ARM PXA320 cpu,
> > qtopia-core-opensource-src-4.3.2, cross-compiling everything with
> > an arm-linux-gxx tested toolchain using no particular compiling
> > flags. I'm working with a linuxfb device, and the test program provided
> > with qtopia (examples/qtopiacore/framebuffer) works perfectly with
> > both 8bpp and 16bpp.
> >
> > Where am I wrong? Can anybody help me?
> >
> > Many thanks,
> > Giorgio
> >
> > --
> > To unsubscribe - send "unsubscribe" in the subject to
> > qtopia-interest-request@xxxxxxxxxxxxx
> >
> >
> >
> >
>
>
>
>
Message 3 in thread
Giorgio Cardarelli wrote:
> Hi Guillaume,
> yes, I'm using qmake from qtopia and running make actually uses
> arm-linux-gxx, building a working arm executable.
>
> I've also connected a slot to the button's click() signal, just to cout
> something to stdout, and even if I cannot see the button (as
> I've mentioned) I can click it and see output on the console.
> On a side note: when I move the cursor on the button, it fades
> away and I cannot see the cursor too!
>
> This, to me, means that I've got only problems in painting widgets
> on linuxfb. The same program with standard qt (on my X11 linuxbox)
> works fine.
>
> I will try, as you suggest, using qtopia-4.3.4, but I think
> the problem is actually somewhere else in the cross-compilation of qtopia
> and/or in the toolchain I'm using.
>
> I've seen in the list's archive that other people had the same
> issue, but no one mentions a solution.
>
> I will let you and the list know if I make any improvement.
>
> Giorgio
>
>
>> This code is ok for me...
>>
>> How do you compile it ?
>>
>> I suppose that you did like this :
>> qmake -project
>> qmake
>> make
>>
>> with the qmake of qtopia (for cross compile)
>>
>> I tested this code on the board AT91SAM9261-EK (arm based) and on my desktop
>> computer and it is working well (see the shot in attachment)
>>
>> Maybe the Qtopia libs are not installed correctly... or try the latest
>> release of qtopia core. I run qtopia-core-opensource-src-4.3.4 on my board.
>>
>>
>> Cheers,
>>
>> Guillaume
>>
>>
>> -------- Message d'origine--------
>> De: Giorgio Cardarelli [mailto:giorgio.cardarelli@xxxxxxxxxxx]
>> Date: mer. 05/03/2008 09:10
>> À: GARDET Guillaume; qtopia-interest@xxxxxxxxxxxxx
>> Objet : Re: RE : No output on framebuffer
>>
>> Hello Guillaume,
>> thanks for your quick reply. Here is the code.
>>
>> #include <QApplication>
>> #include <QPushButton>
>>
>> int main(int argc, char *argv[]){
>> QApplication app(argc, argv);
>> QPushButton myWidget("prova");
>> myWidget.show();
>>
>> return app.exec();
>> }
>>
>> Really looking forward to hearing from your,
>> thanks again,
>>
>> Giorgio
>>
>>
>>
>>> Hello !
>>>
>>> It is maybe an "error" in your code... Could you send your code by mail ?
>>>
>> I
>>
>>> (we) could test it and maybe find something ...
>>>
>>> Cheers,
>>>
>>> Guillaume
>>>
>>>
>>>
>>> -------- Message d'origine--------
>>> De: Giorgio Cardarelli [mailto:giorgio.cardarelli@xxxxxxxxxxx]
>>> Date: mar. 04/03/2008 16:36
>>> À: qtopia-interest@xxxxxxxxxxxxx
>>> Objet : No output on framebuffer
>>>
>>> Hello list,
>>>
>>> I've prepared a small application with a single QPushButton that
>>> does nothing. I can compile the program with no errors, but
>>> when I run it (./qt-test -qws) only the green "desktop" background
>>> and the mouse cursor is displayed, while the button is not painted.
>>> It seems like I can actually see what lies "under" the qtopia
>>> application (in my case the linux console from where I started my
>>> test app).
>>>
>>> I can give some further informations: I'm using an ARM PXA320 cpu,
>>> qtopia-core-opensource-src-4.3.2, cross-compiling everything with
>>> an arm-linux-gxx tested toolchain using no particular compiling
>>> flags. I'm working with a linuxfb device, and the test program provided
>>> with qtopia (examples/qtopiacore/framebuffer) works perfectly with
>>> both 8bpp and 16bpp.
>>>
>>> Where am I wrong? Can anybody help me?
>>>
>>>
Hi Giorgio,
could you run the test application examples/qtopiacore/framebuffer in
the qtopia-core package and send us the console output? Also send me the
contents of the file config.status in your qtopia-core build directory.
(It might be that you need to configure some additional color depths for
instance..)
--
[ signature omitted ]
Message 4 in thread
Hello Håvard,
thank you very much for your prompt response. I've cross-compiled
qtopia-core-opensource-src-4.3.3 and everything solved. I don't know if it
was actually a problem of version 4.3.2 that has been fixed in the next release
or if I did something wrong, but at present all seem to work well.
If you need it, I can send you the informations you've asked.
Regards,
Giorgio
_____
From: Håvard Wall [mailto:hwall@xxxxxxxxxxxxx]
To: Giorgio Cardarelli [mailto:giorgio.cardarelli@xxxxxxxxxxx]
Cc: qtopia-interest@xxxxxxxxxxxxx
Sent: Fri, 14 Mar 2008 08:34:20 +0100
Subject: Re: RE : RE : No output on framebuffer
Giorgio Cardarelli wrote:
> Hi Guillaume,
> yes, I'm using qmake from qtopia and running make actually uses
> arm-linux-gxx, building a working arm executable.
>
> I've also connected a slot to the button's click() signal, just to cout
> something to stdout, and even if I cannot see the button (as
> I've mentioned) I can click it and see output on the console.
> On a side note: when I move the cursor on the button, it fades
> away and I cannot see the cursor too!
>
> This, to me, means that I've got only problems in painting widgets
> on linuxfb. The same program with standard qt (on my X11 linuxbox)
> works fine.
>
> I will try, as you suggest, using qtopia-4.3.4, but I think
> the problem is actually somewhere else in the cross-compilation of qtopia
> and/or in the toolchain I'm using.
>
> I've seen in the list's archive that other people had the same
> issue, but no one mentions a solution.
>
> I will let you and the list know if I make any improvement.
>
> Giorgio
>
>
>> This code is ok for me...
>>
>> How do you compile it ?
>>
>> I suppose that you did like this :
>> qmake -project
>> qmake
>> make
>>
>> with the qmake of qtopia (for cross compile)
>>
>> I tested this code on the board AT91SAM9261-EK (arm based) and on my desktop
>> computer and it is working well (see the shot in attachment)
>>
>> Maybe the Qtopia libs are not installed correctly... or try the latest
>> release of qtopia core. I run qtopia-core-opensource-src-4.3.4 on my board.
>>
>>
>> Cheers,
>>
>> Guillaume
>>
>>
>> -------- Message d'origine--------
>> De: Giorgio Cardarelli [mailto:giorgio.cardarelli@xxxxxxxxxxx]
>> Date: mer. 05/03/2008 09:10
>> À: GARDET Guillaume; qtopia-interest@xxxxxxxxxxxxx
>> Objet : Re: RE : No output on framebuffer
>>
>> Hello Guillaume,
>> thanks for your quick reply. Here is the code.
>>
>> #include
>> #include
>>
>> int main(int argc, char *argv[]){
>> QApplication app(argc, argv);
>> QPushButton myWidget("prova");
>> myWidget.show();
>>
>> return app.exec();
>> }
>>
>> Really looking forward to hearing from your,
>> thanks again,
>>
>> Giorgio
>>
>>
>>
>>> Hello !
>>>
>>> It is maybe an "error" in your code... Could you send your code by mail ?
>>>
>> I
>>
>>> (we) could test it and maybe find something ...
>>>
>>> Cheers,
>>>
>>> Guillaume
>>>
>>>
>>>
>>> -------- Message d'origine--------
>>> De: Giorgio Cardarelli [mailto:giorgio.cardarelli@xxxxxxxxxxx]
>>> Date: mar. 04/03/2008 16:36
>>> À: qtopia-interest@xxxxxxxxxxxxx
>>> Objet : No output on framebuffer
>>>
>>> Hello list,
>>>
>>> I've prepared a small application with a single QPushButton that
>>> does nothing. I can compile the program with no errors, but
>>> when I run it (./qt-test -qws) only the green "desktop" background
>>> and the mouse cursor is displayed, while the button is not painted.
>>> It seems like I can actually see what lies "under" the qtopia
>>> application (in my case the linux console from where I started my
>>> test app).
>>>
>>> I can give some further informations: I'm using an ARM PXA320 cpu,
>>> qtopia-core-opensource-src-4.3.2, cross-compiling everything with
>>> an arm-linux-gxx tested toolchain using no particular compiling
>>> flags. I'm working with a linuxfb device, and the test program provided
>>> with qtopia (examples/qtopiacore/framebuffer) works perfectly with
>>> both 8bpp and 16bpp.
>>>
>>> Where am I wrong? Can anybody help me?
>>>
>>>
Hi Giorgio,
could you run the test application examples/qtopiacore/framebuffer in
the qtopia-core package and send us the console output? Also send me the
contents of the file config.status in your qtopia-core build directory.
(It might be that you need to configure some additional color depths for
instance..)
--
[ signature omitted ]
