[Buildroot] GTK vs Qt

[Thomas Petazzoni <thomas.petazzoni@free-electrons.com>]

Dear Zoran Djordjevic,

On Tue, 20 Nov 2012 02:23:35 -0800 (PST), Zoran Djordjevic wrote:
> OK -let me put question this way. If I successfully compile/run 
> QT program on desktop, and then recompile the same source with
> let's say Builtroot built compiler (for ARM), should I expect that 
> this program will understand -qws option (which I thought is strictly
> related to QtCreator). The only way I succeeded to start Qt demo 
> programs was with -qws. Hope it's more clear question.

Aaah. Ok. No, -qws *has* nothing to do with Qt Creator.

-qws is the option to tell Qt to start the Qt Windowing System.

When you run a Qt application on your desktop, there is already a
windowing system (X.org) and a window manager. So Qt is just a toolkit
like any other, it just draws inside a window provided by the windowing
system.

However, when you build Qt for your embedded system so that it runs
directly on the framebuffer, there is no windowing system provided. So
Qt has its own, that you must enable for the *first* Qt application you
run, using the -qws option.

You can run multiple Qt applications on your embedded system thanks to
this. The first one will have to be started with -qws, the other ones
will automatically connect to the first one thanks to a Unix socket,
and therefore be able to share the screen.

You probably want to read:

 http://doc.qt.digia.com/qt/qt-embedded-architecture.html
 http://doc.qt.digia.com/qt/qt-embedded-running.html

Best regards,

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