Howto configure Konq/e for arm-linux
Keith Kyzivat
konq-e@mail.kde.org
Fri, 14 Mar 2003 12:18:19 -0500
Kentropy wrote:
>Hello
>I have : arm-linux, Qt/e-3.0.4
>Could someone please post which options are needed to cross compile Konquerror/embedded for arm-linux ?
>
I'm not sure what specifically arm supports or not, but in general, you
should be set with most of the defaults...
I'm working on it for PPC8xx ...
Oh yes, you said Qt/E-3.0.4...
The last stable snapshot that Simon made requires Qt/E-2.3.2 (Qt 2
series APIs)..
The current CVS head for kdenox (Konq/E) requires you to have Qt/E-3.1.1
(I'm trying with Qt/E-3.1.2, but Luciano checked it in having tested it
with Qt/E-3.1.1 -- am I right Luciano?).
In General, the xconfigure script that Simon has available in his HTTP
download area is great (1 directory above the snapshots dir). it's a
good generic cross-compiling script. And since you're xcompiling for
arm-linux, I don't believe you have to modify it at all -- I think it
was written for arm.
So, you can go two ways:
* Go grab Qt/E 2.3.2 from Trolltech's website, and go with Simon's
latest snapshot (12-29-2002)
http://devel-home.kde.org/~hausmann/snapshots/konqueror-embedded-snapshot-20021229.tar.gz
(make sure that if you compile Qt/E for multithreaded, that you
also compile Konq/E for multithreaded, and vice versa)
This will get you a Konq/E based on the KDE2 Konq.
* Go with the latest and greatest (luciano put in the patches for
working with KDE3.1 only a few weeks ago)
Grab Qt/E 3.1.x from trolltech
The CVSROOT you want is :pserver:anoncvs.kde.org:/home/kde
cvs co kdenox
cvs co -r KDE_3_1_BRANCH kdelibs
cd kdenox
make -f Makefile.cvs
then you can proceed as you would with the snapshot, i.e.
./configure, etc..
>Can I use Qt/e without QPE ?
>
Yup. I've been doing it. When you get it on your target, just run
konqueror -qws. This'll run directly on the framebuffer without a need
for a launcher, etc.
Of course, if you have an input problem (i.e. can't get to a console or
whatnot), you many want to persue some other technique (I've got Konq
starting from the rc.S startup scripts on my device).
Now, if you want to work with the latest CVS Konq/E, bear in mind, I
have yet to get it totally up and running. It'll be good to have
another datapoint.
I've also figured out that VPaths don't appear to work right now (i.e.
make sure you configure and build from within the source tree itself,
don't make a build directory, and reference the configure script from
there).