From kde-devel  Wed Jan 28 12:31:55 2009
From: Andreas Pakulat <apaku () gmx ! de>
Date: Wed, 28 Jan 2009 12:31:55 +0000
To: kde-devel
Subject: Re: Problem finding libical (kdepimlibs)
Message-Id: <20090128123155.GD6310 () neo ! apaku ! dnsalias ! org>
X-MARC-Message: https://marc.info/?l=kde-devel&m=123314750723661

On 28.01.09 12:09:05, Andreas Pakulat wrote:
> On 28.01.09 12:49:29, Hasso Tepper wrote:
> > Rauch Wolke wrote:
> > > it depens on where your libical includes are stored ....
> > > mine are in /usr/include/libical .... locate them and use this
> > > directory ....
> > 
> > I don't use anything. It's cmake magic which sets it 
> > to /usr/local/include/libical - ie. it (or libical itself?) is buggy 
> > probably.
> 
> That find-module needs a rewrite, it violates almost all guidelines about
> writing find-modules (Sorry Allen).
>  
> > My guess is that it works by accident for you (and most of others) 
> > because /usr/include is in includes path anyway. My "problem" is 
> > that /usr/local/include isn't includes path - I have no more stuff 
> > installed in /usr/local.
> 
> Exactly, the code using ical.h and friends needs to be fixed to use
> 
> #include <libical/ical.h>
> 
> And along with that the find-module needs to be fixed as well.

I'm posting a possible fix to kde-buildsystem, further discussion should
happen there.

Andreas
 
-- 
You will be divorced within a year.
 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<