[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#887827: kcalcore FTCBFS: uses try_run



Control: tags -1 +fixed-upstream

Hey,
upstream now updated the LibIcal.cmake found a solution, that for for all:
https://commits.kde.org/kcalcore/6377808f5b5c46bbc61ecb054b3e59e5abe8959a

hefee

--
On Sonntag, 21. Januar 2018 19:52:15 CET Sandro Knauß wrote:
> Control: tags -1 +upstream
> 
> This is a upstream issue and Debian should not modify this when possible.
> I pushed a modified patch to the phabricator instance:
> https://phabricator.kde.org/D10011
> 
> hefee
> 
> --
> 
> On Samstag, 20. Januar 2018 12:48:28 CET Helmut Grohne wrote:
> > Source: kcalcore
> > Version: 4:17.08.3-1
> > Tags: patch upstream
> > User: helmutg@debian.org
> > Usertags: rebootstrap
> > 
> > kcalcore fails to cross build from source, because it uses try_run from
> > cmake to figure out the version of libical. Sadly, libical only makes
> > this easily testable with try_compile in version 3.0 and kcalcore still
> > uses 2.0. The version is a macro that becomes a string (in <3.0). We
> > cannot reasonably extract that with try_compile. Bummer.
> > 
> > Fortunately, libical provides a pkg-config file and that file ships a
> > version. Thus we can use pkg-config to extract the version. This also
> > means that we no longer have to guess what libraries to link to or the
> > like as the pkg-config file knows about such things. It all becomes a
> > lot easier.
> > 
> > After applying the attached patch (and adding pkg-config to
> > Build-Depends), kcalcore cross builds successfully. Can you apply it?
> > 
> > Helmut

Attachment: signature.asc
Description: This is a digitally signed message part.


Reply to: