KDE binary factory

[Gilles Caulier]

For the moment, the only advantage to KDE binaries factory is to build
Windows bundle with MSVC. As we will need MSVC to build QtWebEngine which
cannot be cross compiled with Mingw (thanks google to increase the puzzle
with Chrome core implementation), it can be a solution.

Note : i refuse to use a Windows computer (or through VM), to compile with
MSVC. I do it currently in my office to compile a Qt framework that i
written, and MSVC is just a big pain. The scripting language under Windows
is just archaic and a waste of time.

For compatibility with external shared libraries under Windows, I cannot
cross compile in my office. It's just the hell...

Gilles Caulier

2018-08-17 0:55 GMT+02:00 Andrey Goreev <aegoreev at gmail.com>:

> Gilles,
>
> I never heard of that resource before, thanks for sharing.
> Now I have Dolphin on my Windows machine :)
>
> Best regards,
> Andrey
>
> On Thu, Aug 16, 2018 at 6:43 AM Gilles Caulier <caulier.gilles at gmail.com>
> wrote:
>
>> Hi all,
>>
>> I don't yet investigate how to branch digiKam source code to the Jenkins
>> CI service from KDE to build binaries version for Windows, AppImage,
>> Flatpack, and MacOS.
>>
>> https://binary-factory.kde.org/
>>
>> I know that Windows binaries are compiled with MSVC.
>> I know that MAcOS is not well supported for the moment.
>> I know that we will need to use craft framework.
>>
>> I'm not very well impatient to try this service if i need to pass again 6
>> months of development. My shell scripts to build all bundles work already,
>> are certainly not perfect, but do the job. Sure it work locally, not in a
>> continuous integration service, but it work...
>>
>> Any feedback here about KDE binary factory ?
>>
>> Best
>>
>> Gilles Caulier
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/digikam-devel/attachments/20180817/1622026f/attachment.html>