[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-kimageshop
Subject:    Re: Next Gen CI Will Be Moving to Production Shortly: Upcoming Changes
From:       Ben Cooksley <bcooksley () kde ! org>
Date:       2017-05-16 17:51:06
Message-ID: CA+XidOEugpTFg0v=5Rr6f-k4u_iFQiSRDhMHPXm-Gpap=SeJeQ () mail ! gmail ! com
[Download RAW message or body]

On Tue, May 16, 2017 at 11:29 PM, Dmitry Kazakov <dimula73@gmail.com> wrote:
>
>>> For Windows we have the following problems:
>>>
>>> 1) Krita needs MinGW for compiling on Windows
>>
>> How hard a requirement is this? From what I understand it's related to
>> the G'Mic code correct?
>> Chances are we'll introduce Mingw at some point, but it's not on my
>> immediate plans (the design makes it not too hard, but i'd prefer to
>> push MSVC a good part of the way to workable first)
>
>
> Well, of course, if we disable GMic and Vc, we will still be able to build
> Krita itself. But, then, it will be a question of the purpose of CI. Just
> testing for compilation error and unittest failures is a nice purpose. But
> we would also like to have it build the user-targeted nightly/stable
> packages. And that will be impossible with without at least Vc.

I would suggest we have a different setup for producing nightlies &
final binaries as the CI builds in full debug mode, which means
asserts are enabled and no optimization is done by the compiler.

This means that performance probably will suck to an extent especially
in performance sensitive code, and we probably want to give a more
optimal user experience, even with Nightly binaries...

With G'Mic going away, shall we give it a try and see what happens
with Vc with the latest MSVC?

>
> --
> Dmitry Kazakov
>

Cheers,
Ben
[prev in list] [next in list] [prev in thread] [next in thread]