[KDE-India] Install Problem

[Till Adam]

On Tuesday 27 June 2006 10:06, Deepak Kumar Mishra wrote:

>  I am trying to install Konq-Embedded.
> on my x86 system I have installed the kernel and gcc tool chain.
> I dont have Xwinwors installed
> I have downloaded the following versions of QT and kde
>
> QT  qt-embedded-eval-3.3.6.tar.gz
> Konq konqueror3-embedded-0.2-20060121.tar.tar

I seem to remember konq-embedded working against QTopia, and thus Qt 2, 
but I might be wrong.

> I dont want to recompile my kernel to enable frame buffer.
> I have few questions now.
>
> 1. If I want to use qvfb , I think I should have Xserver installed. (
> is this true?)

Yes, qvfb is a normal X application. It's a window showing the contents 
of a framebuffer as a pixmap, basically.

> 2. to use Virtual Frame buffer , the guide says "Make sure
> QT_NO_QWS_VFB in $QTDIR/src/tools/qconfig.h is not defined and
> compile the Qt/Embedded library. " I dont understand this properly.
> when I use the above version of QT,  in in $QTDIR/src/tools/
> directory I dont have a qconfig.h file but I have  qconfig-dist.h,
> qconfig-small.h, qconfig-medium.h .. files.. So how do i go ahead?

You don't have to do anything, since you want qvfb and that's the 
default, I believe.

> 3. The virtual frame buffer guide says "Compile qvfb as a *normal
> Qt/X11 application* and run it - do not compile it as a Qt/Embedded
> application." can any one please explain me properly .. how to do
> this?

As mentioned qvfb is a normal X application, and thus needs to be 
compiled against the X version of Qt. Not against the embedded version, 
since it does not display on the framebuffer, but on X. This will be 
Qt3, in your case.

> 4. what does this mean "Start a Qt/Embedded master application (i.e.
> construct QApplication with QApplication::GuiServer flag or use the
> -qws command line parameter)."

On QtEmbedded there needs to be one application that is the "master", 
which is in charge of distributing events, etc. You can make an 
application the master eithre by starting it with the -qws command line 
switch, or by setting the a bove mentioned flag when constructing your 
QApplication instance. The second or nth application you start on the 
same system does not need that, it will find and connect to an alreayd 
rnuning master.

Hope that helps,

Till
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://mail.kde.org/pipermail/kde-india/attachments/20060627/49725d4a/attachment.pgp