Next Gen CI Will Be Moving to Production Shortly: Upcoming Changes

[Dmitry Kazakov]

The only trouble for Krita will be Windows builds, but it is not a 
regression, so we can proceed with the move.

For Windows we have the following problems:

1) Krita needs MinGW for compiling on Windows
2) We have a set of cmake scripts that builds all the deps on Windows. 
Sometimes the scripts apply some patches. So if we would like to reuse 
the builds done by CI system for "nightly" packages (and we would really 
like to!), so these custom dependency builds should also be integrated 
somehow. How to do that within the limits of the new dependencies framework?

Here is the list of the deps we build on Windows (and for Linux AppImage 
packages):
https://cgit.kde.org/krita.git/tree/3rdparty

And here is the list of patches we apply on them:

./ext_exiv2/exiv2.patch
./ext_exiv2/tzname.patch
./ext_exiv2/patch_mingw.patch
./ext_iconv/iconv-src-1.13.1.patch
./ext_ocio/patch_mingw.patch
./ext_openexr/patch_mingw.patch
./ext_poppler/poppler_mingw.patch
./ext_vc/vc1.2_malloc_free.patch
./ext_qt/0001-Don-t-request-the-MIME-image-every-time-Windows-asks.patch
./ext_qt/0002-Hack-always-return-we-support-DIBV5.patch
./ext_qt/0003-Hack-for-fullscreen-workaround.patch
./ext_qt/mac-default.patch
./ext_qt/qtbase-configure.patch




On 16.05.2017 13:02, Boudewijn Rempt wrote:
> On Sat, 6 May 2017, Ben Cooksley wrote:
>
>> Which brings me to the third point of attention. We'll only be adding
>> projects to the Next Gen CI system at their request going forward.
> Krita should be part of this, too. We don't need anything special or
> up to date, our frameworks requirements are very modest.
>

-- 
Dmitry Kazakov