Subject: Re: kdevelop-20000322
To: None <>
From: Berndt Josef Wulf <>
List: tech-pkg
Date: 03/26/2000 08:34:55 wrote
> > 
> > Hmm, would you have time to look at the pkgsrc for KDevelop on
> > 
> > 
> > What do I need to do? Is it enough to supply the configure arguments
> > 
> > --with-qt-include=${X11BASE}/include/qt1 etc.... ?
> for most of the kde* pkgs, I had to:
> 1) modify the pkg Makefile as you noted
> 2) edit the configure script and change
>     moc -> moc1
>     -lqt -> -lqt1
> for kdevelop I also had to edit
> pkgsrc/devel/kdevelop/work.i386/kdevelop-1.0/kdevelop/
> and change "-lqt" to "-lqt1"
> I have to admit that I'm not a KDE user at all.  My only interest is to be
> able to upgrate Qt since cad/vipec needs the newer Qt.  But I couldn't
> justify breaking KDE for that.

This is easy enough to implement, the problem is that in case of
Kdevelop all project templates using the qt stuff will nolonger work.
They are all packed up in tar.gz archives and using project templates
is what make KDevelop so powerful.


I can't see an easy way of fixing this.

In hinsight, wouldn't it be easier to call the new qt-2.x stuff
libqt2 and moc2 and left libqt stuff alone? 

cheerio Berndt
Name    : Berndt Josef Wulf            | +++ With BSD on Packet Radio +++
E-Mail  :             |    tfkiss, tnt, dpbox, wampes
ICQ     : 18196098                     |  VK5ABN, Nairne, South Australia 
URL     : | MBOX :
Sysinfo : DEC AXPpci33+, NetBSD-1.4    | BBS  : vk5abn.#lmr.#sa.aus.oc