KF5 Porting Notes

2016-01-06 Thread Martin Koller
In the section about KApplication -> QApplication, I find: Make sure to: Call QCoreApplication::setApplicationName() and others ... It seems this is not needed when one uses KAboutData::setApplicationData() If this is correct, I would add this to the page:

Re: Policy regarding QtWebKit and QtScript

2016-01-06 Thread Kevin Kofler
I've been digging deep into QtWebEngine in the hope of to polishing it up for Fedora (which sounds less hopeless now that Fedora has become less strict on bundled libraries), seeing how QtWebKit has no future with nobody fixing security bugs in it, so let me clear up a few misconceptions in

Re: Policy regarding QtWebKit and QtScript

2016-01-06 Thread Kevin Kofler
Adriaan de Groot wrote: > - Why am I building ninja when it's already packaged externally? export NINJA_PATH=/usr/bin/ninja (or ninja-build or however your OS's package calls the binary) is enough to fix that. > - Why am I building yasm? Add GYP_CONFIG += "use_system_yasm=1" to your

Re: KF5 Porting Notes

2016-01-06 Thread Albert Astals Cid
El Wednesday 06 January 2016, a les 14:56:48, Martin Koller va escriure: > In the section about KApplication -> QApplication, I find: > > Make sure to: > Call QCoreApplication::setApplicationName() and others ... > > It seems this is not needed when one uses KAboutData::setApplicationData()

Jenkins-kde-ci: kdelibs KDE-4.14 latest-qt4 » Linux,gcc - Build # 52 - Still Unstable!

2016-01-06 Thread no-reply
GENERAL INFO BUILD UNSTABLE Build URL: https://build.kde.org/job/kdelibs%20KDE-4.14%20latest-qt4/PLATFORM=Linux,compiler=gcc/52/ Project: PLATFORM=Linux,compiler=gcc Date of build: Wed, 06 Jan 2016 23:03:05 + Build duration: 12 min CHANGE SET Revision

Jenkins-kde-ci: kdelibs KDE-4.14 stable-qt4 » Linux,gcc - Build # 49 - Still Unstable!

2016-01-06 Thread no-reply
GENERAL INFO BUILD UNSTABLE Build URL: https://build.kde.org/job/kdelibs%20KDE-4.14%20stable-qt4/PLATFORM=Linux,compiler=gcc/49/ Project: PLATFORM=Linux,compiler=gcc Date of build: Wed, 06 Jan 2016 23:03:05 + Build duration: 12 min CHANGE SET Revision

Re: Policy regarding QtWebKit and QtScript

2016-01-06 Thread Adriaan de Groot
Kevin, first off thank you for responding so carefully to Vadim and to me. It does make a difference to porting efforts. On Wednesday 06 January 2016 18:11:25 Kevin Kofler wrote: > unbundling doesn't seem to be the main focus. And the reason there are so > many patches is because they produced a

Re: Policy regarding QtWebKit and QtScript

2016-01-06 Thread Kevin Kofler
Adriaan de Groot wrote: > Kevin, first off thank you for responding so carefully to Vadim and to me. > It does make a difference to porting efforts. I'm glad to be of help. I also spent quite some time fighting with this thing and I'm not entirely done yet, so I know how you feel. And you guys