[PATCH] akonadi can't be built in kdesupport

Matthew Woehlke mw_triad at users.sourceforge.net
Mon Jun 22 21:38:08 CEST 2009

Alexander Neundorf wrote:
> On Wednesday 17 June 2009, Matthew Woehlke wrote:
>> Alexander Neundorf wrote:
>>> On Monday 15 June 2009, Matthew Woehlke wrote:
>>>> (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.)
>>> I don't understand that paragraph. Can you please explain ?
>> As in... akonadi was described as:
>> - try to find soprano
>> - if we didn't find it, check if we are in kdesupport
>>    - if so, use soprano from kdesupport
>> ("prefer install[ed] soprano")
>> I suspect the norm is:
>> - check if we are in kdesupport
>>    - if yes, use foolib from kdesupport (i.e. from source/build dir, not
>> as installed)
>>    - else look for foolib as usual
>> ("prefer source foolib")
> You are right here too, I would also prefer that order of checking, seems more 
> straightforward to me.

Looking again, it seems like akonadi/CMakeLists.txt /should/ be doing 
the right thing here. I am confused. Apparently I am going to remain 
confused until this problem pops up again. Annoying :-).

Anyway, appreciate the discussion, I have a much better idea what to dig 
into if I see this again. Thanks, all.

Until then... RESOLVED -> WORKSFORME ;-)

Please do not quote my e-mail address unobfuscated in message bodies.
"Have you tried that new mixed drink, 'GDR'"?
"What is it?"
"Gin, Duck and Rum. It tastes fowl."

More information about the Kde-buildsystem mailing list