[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: Newbie Guide to Building KDE from CVS. Comments sought.
From:       Nicolas Goutte <nicolasg () snafu ! de>
Date:       2003-09-14 17:38:30
[Download RAW message or body]

Try to use DO_NOT_COMPILE with Kexi:
DO_NOT_COMPILE="kexi" ./configure

Kexi is not stable and will not be released as part of Koffice 1.3.

As for configure's comments, you can compile without (if you will not miss the 
features.)
- The MS Word import filter is not compilable for now either.
- ImageMagick is for Krita, which is also unstable and not part of Koffice 
1.3.

(But as you see, you get CVS HEAD typical problem, but not so much a load than 
a full KDE CVS HEAD. That is what I tried to tell.)

As for admin, I do not know, but it seems to have been problems there. (See 
the other thread about the Perl error messages.)

The correct address of KOffice is http_//www.koffice.org (the other one is the 
old one, I do not know if it still work.)

QSA is Qt's script languages. (It is need in Kexi if I am well informed.)

Have a nice day!

On Sunday 14 September 2003 18:14, Gary Cramblitt wrote:
> On Sat, 13 Sep 2003 22:36:54 +0200
>
> Nicolas Goutte <nicolasg@snafu.de> wrote:
> > Sorry! Either you misunderstood me or I was not clear enough (must be the
> > last one.)
> >
> > I am not telling that users should not come to CVS HEAD. I am also not
> > telling that Gary's tutorial is bad, not needed, not useful...
> >
> > I am just trying to explain that jumping directly into CVS HEAD might be
> > too much (not everybody has the hardware, patience, time... to do build
> > after build after build.)
>
> OK, I agree that your approach is a good one for the newbie.  Since I
> haven't tried your approach, I don't think I'm qualified to write about
> it at this time.  Perhaps someone else is willing to write such an
> article?  I did add some words to my article mentioning your approach
> and refering the reader to koffice.kde.org.
>
> BTW, KOffice is one of the few remaining modules I haven't been able to
> build from CVS HEAD yet.  FWIW, here's the error messages from a build
> attempt on Sep 13th.
>
> *** Postprocessing Makefile templates
> Malformed UTF-8 character (unexpected non-continuation byte 0x20,
> immediately after start byte 0 xdf) in pattern match (m//) at admin/am_edit
> line 2029.
> <About half a dozen more messages similar to above>
> configure: WARNING: qsa >= 20030301 could not be found anywhere, kexi will
> compile without scrip ting support. check ftp.trolltech.com for qsa
> >=20030301
> The MS Word filter won't be compiled due to experimental changes.
> Your libaspell is too old or not installed, I couldn't find aspell.h.
> You must download aspell >= 0.50.2
> See http://aspell.net/. Spell-checking disabled.
> You're missing ImageMagick (>=5.5.2). krita will not be compiled.
> You can download ImageMagick from http://www.imagemagick.org/
> In file included from
> /home/share/src/kde/koffice/kexi/core/filters/kexitableimportsourceiface.c
> pp:20:
> /home/share/src/kde/koffice/kexi/core/filters/kexitableimportsourceiface.h:
>25:32: kexiDB/kexidbt able.h: No such file or directory
>
> Clearly, I need to follow configure's advice and install the packages it
> mentions, although I'm curious what this "qsa" thingy is.  Just haven't
> had time to work on it yet.
>
> Thank you for your input.
>
> Regards,
> Gary Cramblitt
>
> >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to
> >> unsubscribe <<

 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

[prev in list] [next in list] [prev in thread] [next in thread]