That's because the scanning in configure.in only looks for specific strings, and the one currently returned by evolution doesn't match the pattern.
This is easily fixed by adding a dot instead of a space on line 12 in
configure.in, it should look
like this :
EVO_VER=`evolution --version | sed -e 's/.nome .volution.//g'`
This is only one of the many inconsistencies I stumbled on last week
when trying the same thing.
I eventually gave up on it, I'm now in the process of
porting the OpenSync evolution2 plugin to MultiSync.
I'll let you know when I have something that works.
Question: are others trying the same thing?
Danny
On Mon, 2005-07-18 at 18:21 +0100, Paul Hunnisett wrote:
> I am trying to compile the evolution 2 plugin for multisync and get the
> following error:
>
> configure: error: This version of the Evolution plugin only works with
> Evolution >= 1.5
>
> But, I am running evolution 2.2.3. Is anyone able to tell me how to get
> configure to correctly identify the evo version number?
>
> Paul
>
>
>
> -------------------------------------------------------
> SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
> from IBM. Find simple to follow Roadmaps, straightforward articles,
> informative Webcasts and more! Get everything you need to get up to
> speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
> _______________________________________________
> Multisync-users mailing list
> Multisync-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/multisync-users
>
--
Danny Backx ; danny.backx - at - scarlet.be ; http://danny.backx.info
signature.asc
Description: This is a digitally signed message part
