In D19740#442141, @staniek wrote:

BTW is it possible to get KDE certificate for the installer?

I've found only this older thread: https://www.mail-archive.com/kde-community@kde.org/msg03833.html

Sorry, forgot about it.
Which package is actually broken? python?
When was your craft install?

In D19740#438300, @staniek wrote:

• KEXI: ignore hunspell and qtlocation/sensors/qqcontrols2
• Simplify blacklist for KEXI, ignore more files
• NSIS Installer for KEXI: Improve start menu and install dir removal (remove parent KEXI folder if makse sense), fix folder names

So then the workaround is correct, I haven't tried whether the original code compiles with CMAKE_CXX_STANDARD=17

To manage this review you can use arcanist (craft arcanist).
https://secure.phabricator.com/book/phabricator/article/arcanist_diff/

The main difference for a Qt application not marked as gui/WIN32 is that a console Windows will pop up when the application is executed.

Thx!

Msvc2017.
I think frameworks is still c++11?

aren't valid file names on windows, and look strange for unix too

• Fix build with msvc

first wave

I had it too.
Your issue is on Windows? Actually craft should use the one from the settings directly and not python from the path.

The problem is that QWebengine is msvc2017 only and most Skrooge deps are mingw only.

I tried to fix the webkit build with mingw once but I don't have the time to go after it.
A good source for patches is https://github.com/msys2/MINGW-packages/tree/master/mingw-w64-qtwebkit

Merged
https://invent.kde.org/kde/juk/commit/f58970389eea48cca189abead796440aae127d54

I should go to phabricator more often....

Hi I forgot about this sry.