Re: Problem using Vc with CMake 3.0 and kf5

2015-05-25 Thread Alex Merry
On Monday 25 May 2015 15:31:52 Boudewijn Rempt wrote: > http://www.valdyas.org/~boud/vc-cmake-3.tgz is as minimal as I know how to > make it: you still need qt, KDELibs4Support and extra-cmake-modules > installed. After that, running cmake and make VERBOSE=1 will give the > exact problem I've got.

Re: Problem using Vc with CMake 3.0 and kf5

2015-05-25 Thread Alex Merry
On Monday 25 May 2015 13:50:08 Boudewijn Rempt wrote: > On Mon, 25 May 2015, Alex Merry wrote: > > Ah, yes. You may get somewhere with > > include_directories($) > > > > Basically, this should replace all those semicolons in the generated > > output > > wit

Re: Problem using Vc with CMake 3.0 and kf5

2015-05-25 Thread Alex Merry
On Monday 25 May 2015 13:03:40 Boudewijn Rempt wrote: > On Mon, 25 May 2015, Alex Merry wrote: > > The issue here is that Vc's macros implicitly assume that all compilation > > flags (including include paths) are done at the directory level (with > > include

Re: Problem using Vc with CMake 3.0 and kf5

2015-05-25 Thread Alex Merry
On Saturday 23 May 2015 11:51:55 Boudewijn Rempt wrote: > Sorry for the extensive cross-posting in advance, please when replying, do > a reply-all. > > Just so everyone is on the same page: Vc is a template library that makes > it easy to build vectorized code using a single source file. Krita use

Re: debugfull -> debug

2015-05-10 Thread Alex Merry
On Thursday 07 May 2015 22:57:47 Jaroslaw Staniek wrote: > Hi, > As with some other bits of knowledge during porting today I just share this > one: > > https://community.kde.org/index.php?title=Calligra/Building/3&diff=42353&old > id=42349 > > When you use Qt4/KF5, debugfull is dead [1] so you'd