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

List:       kde-buildsystem
Subject:    Fwd: KDE/kdebase/libkonq
From:       coolo () kde ! org (Stephan Kulow)
Date:       2006-03-01 14:19:47
Message-ID: 200603011519.49143.coolo () kde ! org
[Download RAW message or body]

Am Mittwoch, 1. M?rz 2006 15:14 schrieb David Faure:
>
> Doesn't sound like portable solution to me.
>
> I mean if that's the only way to know which kde libs kparts depends upon,
> then it won't work on windows and we need another solution there anyway, so
> why not do it always the same:
>
> When writing ${LIB_KPARTS} we -know- that this means
>    kparts+kio+kdeui+kdecore+kdefx+dcop+qtxml+qtgui+qtcore,
> and this can be changed in one cmake module easily (with nested aliases of
> course, so in fact it should be ${LIB_KPARTS}=kparts+${LIB_KIO} ).
>
> If you mean the stuff under Qt, like X and zlib then ok, pkgconfig would be
> ok for those.
I want to define the dependencies of kparts _once_ - not in two cmake files.
Because that asks for trouble. It did in the past and it will in the future. 
And we want to offer pkg-config files anway. I kind of doubt, pkg-config is 
so unportable code.

Greetings, Stephan

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