struggling to build KDev4

Marek Jasovsky jasovsky.marek at gmail.com
Fri Aug 22 16:37:24 UTC 2008


Hi

I have successfully built kdelibs (trunk) into $HOME/kde4 but now I am
not sure, how to tell cmake (for kdevplatform) that it should use
kdelibs from $HOME/kde4 and not from original locations. how should I
do this?

(I did not previously do such linux development, that's why my
questions might seem simple, or strange.

thanks a lot

Marek

2008/8/22, dizzy <dizzy at roedu.net>:
> On Friday 22 August 2008 16:59:36 Marek Jasovsky wrote:
>> Andreas, is this some typo, or you really mean that I should build
>> WHOLE KDE4 from scratch, to some temp dir and then use this build to
>> run kde apps?
>
> The problem is current kdev4 requires kdelibs from trunk (it doesn't work
> with
> 4.1.x kdelibs). As such you need to build those yourself unless you have
> some
> distribution with trunk kdelibs. What some people do is build kdev4 and all
> dependencies into that directory (notice that does not mean "WHOLE KDE4", it
> just means kdevplatform, kdelibs and deps of that).
>
> My current solution is to have kde 4.1 DE installed system wide from Gentoo
> kdesvn-portage ebuilds (this automatically takes care of installing all
> those
> dependencies for kdelibs and such). I also have in parallel (still system
> wide) kdelibs from trunk (as there are ebuilds for that too). Then, I build
> and install only kdevplatform/kdev4 into ~/kde4 (so I can update/patch/etc
> without the hassle of messing with ebuilds).
>
> You seem to be using OpenSUSE, I think there are already rpm's with kde 4.1
> Try to install those (and their deps) and then try just to build kdelibs,
> kdevplatform, kdevelop4 into ~/kde4 using the same deps (I didn't noticed
> kdelibs trunk requiring anything more than kdelibs 4.1 do).
>
> --
> Dizzy
> 			"Linux is obsolete" -- AST
>
>
> _______________________________________________
> KDevelop-devel mailing list
> KDevelop-devel at kdevelop.org
> https://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-devel
>




More information about the KDevelop-devel mailing list