[PATCH] akonadi can't be built in kdesupport

Matthew Woehlke mw_triad at users.sourceforge.net
Mon Jun 15 21:45:53 CEST 2009


Andreas Pakulat wrote:
> On 15.06.09 14:26:22, Matthew Woehlke wrote:
>> Alexander Neundorf wrote:
>>> Still, why doesn't the cmake code from kdesupport/akonadi/CMakeLists.txt work 
>>> for you ?
>> I think it gets confused when soprano is no longer in the location 
>> specified in the cache. I'm working on reproducing now,
> 
> Well, then update the cache or remove it. I've just had the same problem
> with kdepimlibs and Akonadi. If the cached values get invalid, its your
> job to fix them, not cmake's.

...except that akonadi is/was the only part of KDE (out of the pretty 
decent chunk I build) that has/had problems here. I've had akonadi, and 
/only/ akonadi, cause problems in the described cycle on at least one - 
and I think two or three - previous occasion(s).

But something seems to have changed, as it's not happening right now.

(I suspect akonadi might be "weird" in that other bits of kdesupport 
prefer source to install for their own kdesupport dependencies, such 
that they never wind up pointing to $KDEDIR. But that's just a WAG.)

-- 
Matthew
Please do not quote my e-mail address unobfuscated in message bodies.
-- 
End of Transmission



More information about the Kde-buildsystem mailing list