---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/122268/
---
(Updated April 3, 2015, 1:34 p.m.)
Status
--
This change has been di
On Fri, 3 Apr 2015, Boudewijn Rempt wrote:
On Fri, 3 Apr 2015, Alexander Richardson wrote:
2015-04-03 10:08 GMT+02:00 Boudewijn Rempt :
I've got a problem porting calligra to kf5 that I don't know how to solve.
We use a 3rd party library called Vc, which does vectorization for us. It
takes
On 02/04/15 21:29, Stephen Kelly wrote:
>> I have no particular objection,
>
> So, what needs to be done to get this synced up? Bump the version in
> the CMakeLists.txt and update some release-tarball-creating script?
> David I guess the latter is for you?
>
> Thanks,
>
> Steve.
Can we at least
On Fri, 3 Apr 2015, Alexander Richardson wrote:
2015-04-03 10:08 GMT+02:00 Boudewijn Rempt :
I've got a problem porting calligra to kf5 that I don't know how to solve.
We use a 3rd party library called Vc, which does vectorization for us. It
takes a certain object file and builds it for differ
2015-04-03 10:08 GMT+02:00 Boudewijn Rempt :
> I've got a problem porting calligra to kf5 that I don't know how to solve.
>
> We use a 3rd party library called Vc, which does vectorization for us. It
> takes a certain object file and builds it for different processor
> architecturres. In order to d
I've got a problem porting calligra to kf5 that I don't know how to solve.
We use a 3rd party library called Vc, which does vectorization for us. It
takes a certain object file and builds it for different processor
architecturres. In order to do that, it generates a new gcc line for every
arch
