new (?) cmake problem with libalkimia version

[Jack]

Thanks.  I was using alkimia from git head in hopes of testing the new  
online quote stuff, but still have some other things to deal with  
first.  (Fortunately, I finally found an online quote service and  
settings that work for me.)

Jack

On 2018.12.18 16:05, Thomas Baumgart wrote:
> Hi,
> 
> I have the exact same change here but was not sure that someone is  
> using the new version of LibAlkimia with 5.0. So I just pushed it.
> 
> Regards
> 
> Thomas
> 
> On Dienstag, 18. Dezember 2018 19:23:46 CET Andrew Ho wrote:
> 
> > The version of kmymoney i test is git-050c7d17.
> >
> > The version of libalkimia-8.0.0.
> >
> > This CMakeList.txt is
> >
> > find_package(LibAlkimia5 8.0.0)
> > if (NOT LibAlkimia5_FOUND)
> >    find_package(LibAlkimia5 7.0.0 REQUIRED)
> > endif()
> >
> > That means either LibAlkimia5-8.0.0 or LibAlkimia5-7.0.0.
> >
> > I confirm that libAlkimia5-8.0.0 is working.
> >
> > Thanks,
> >
> > --
> >
> > On 2018-12-18 12:16 p.m., Jack Ostroff wrote:
> > > I just tried recompiling from git head branch 5.0.  It claimed it
> > > could not find an appropriate configuration file for libalkimia5.  
> It
> > > found version 8.0.0 of the relevant cmake files, which are there
> > > because I currently have libalkimia installed from git head.  For  
> now,
> > > I'll just reinstall the released libalkimia.  My question is  
> whether
> > > we do need to restrict libalkimia to version 7.0.0 or if it would  
> be
> > > OK to allow >= instead of just =.
> > >
> > > Jack
> >
> 
> --
> 
> Regards
> 
> Thomas Baumgart
> 
> https://www.signal.org/       Signal, the better WhatsApp
> -------------------------------------------------------------
> Linux - Life is too short for reboots
> -------------------------------------------------------------
>