Re: KDE4Support Headers
On Friday 03 January 2014 22:38:28 Christoph Cullmann wrote: Hi, KDE4Support installs still stuff like kmimetype.h in the KF5 directory, shall it not better install all its compat headers in some KDE4Support prefix to avoid that one can use them without using KF4::KDE4Support? Excellent point. Fix coming up. -- David Faure, fa...@kde.org, http://www.davidfaure.fr Working on KDE, in particular KDE Frameworks 5 ___ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
compile error
Building KIO: In file included from /home/dh/kde/kf5/src/frameworks/kio/src/core/filecopyjob.cpp:27:0: /home/dh/kde/kf5/usr/include/KF5/KI18n/KLocalizedString:1:36: fatal error: ki18n/klocalizedstring.h: No such file or directory #include ki18n/klocalizedstring.h ^ compilation terminated. Setup: $ pwd /home/dh/kde/kf5/usr/include/KF5/KI18n $ ls -1 ki18n_export.h KLocalizedString klocalizedstring.h KuitMarkup kuitmarkup.h KuitSetup kuitsetup.h I guess this is easy to fix, if you know how... ;) Greetings, Dominik ___ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
Re: compile error
On Saturday 04 January 2014 13:33:59 Dominik Haumann wrote: Building KIO: In file included from /home/dh/kde/kf5/src/frameworks/kio/src/core/filecopyjob.cpp:27:0: /home/dh/kde/kf5/usr/include/KF5/KI18n/KLocalizedString:1:36: fatal error: ki18n/klocalizedstring.h: No such file or directory #include ki18n/klocalizedstring.h ^ compilation terminated. Setup: $ pwd /home/dh/kde/kf5/usr/include/KF5/KI18n $ ls -1 ki18n_export.h KLocalizedString klocalizedstring.h KuitMarkup kuitmarkup.h KuitSetup kuitsetup.h I guess this is easy to fix, if you know how... ;) Greetings, Dominik Removing all the build folders did the trick. Sorry for the noise ;) Dominik ___ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
KF5 include problems on the build.kde.org?
Hi,
I am currently struggling to have the KF5 port of Okteta not only build
locally (what it does fine), but also on KDE's build server:
could anybody hint to me why on the build server the file KLocalizedString is
not found for include on building of the static lib kastencoretestio:
From http://build.kde.org/job/okteta_master_qt5/8/console :
--- 8 ---
13:23:17
/srv/jenkins/workspace/okteta_master_qt5/libs/kasten/core/tests/testdocumentfileloadthread.cpp:28:28:
fatal error: KLocalizedString: No such file or directory
--- 8 ---
libs/kasten/core/tests/CMakeLists.txt has this:
--- 8 ---
set( kastencoretestio_LIB_SRCS
testdocumentfileloadthread.cpp
[...]
)
add_library( kastencoretestio STATIC ${kastencoretestio_LIB_SRCS} )
target_link_libraries( kastencoretestio LINK_PUBLIC Qt5::Core )
target_link_libraries( kastencoretestio LINK_PRIVATE KF5::I18n KF5::CoreAddons
Qt5::Core )
--- 8 ---
Locally I see no problem with the problem, and the setup seems proper:
The file KLocalizedString is inside the KI18n include dir as expected, and
also the KDE4 variant is outside the used includes dirs.
$ ls /home/koder/System/kf5/include/KF5/KI18n
ki18n_export.h KLocalizedString klocalizedstring.h KuitMarkup kuitmarkup.h
KuitSetup kuitsetup.h
$ find /usr/include/ -name KLocalizedString
/usr/include/KDE/KLocalizedString
$ VERBOSE=1 make
[ 0%] Building CXX object
libs/kasten/core/tests/CMakeFiles/kastencoretestio.dir/testdocumentfileloadthread.cpp.o
cd
/home/koder/Kode/kdegit/KDE/kdesdk/build.debug/okteta.kf5/libs/kasten/core/tests
/usr/bin/c++ -DKCOREADDONS_LIB -DQT_CORE_LIB -
DQT_DISABLE_DEPRECATED_BEFORE=0 -DQT_NO_CAST_FROM_ASCII -
DQT_NO_CAST_FROM_BYTEARRAY -DQT_NO_CAST_TO_ASCII -DQT_USE_QSTRINGBUILDER -
D_BSD_SOURCE -D_GNU_SOURCE -D_LARGEFILE64_SOURCE -D_XOPEN_SOURCE=500 -
std=c++0x -Wnon-virtual-dtor -Wno-long-long -Wundef -Wcast-align -Wchar-
subscripts -Wall -W -Wpointer-arith -Wformat-security -fno-exceptions -
DQT_NO_EXCEPTIONS -fno-check-new -fno-common -Woverloaded-virtual -
Werror=return-type -fvisibility=hidden -fvisibility-inlines-hidden -Wall -
std=c++0x -fno-rtti -g3 -fno-inline -fPIC -
I/home/koder/Kode/kdegit/KDE/kdesdk/build.debug/okteta.kf5/libs/kasten/core/tests
-I/home/koder/Kode/kdegit/KDE/kdesdk/okteta.kf5/libs/kasten/core/tests -
I/home/koder/Kode/kdegit/KDE/kdesdk/okteta.kf5/libs/kasten/core/entity -
I/home/koder/Kode/kdegit/KDE/kdesdk/okteta.kf5/libs/kasten/core/document -
I/home/koder/Kode/kdegit/KDE/kdesdk/okteta.kf5/libs/kasten/core/io -
I/home/koder/Kode/kdegit/KDE/kdesdk/okteta.kf5/libs/kasten/core/io/filesystem
-I/home/koder/Kode/kdegit/KDE/kdesdk/okteta.kf5/libs/kasten/core/system -
I/home/koder/Kode/kdegit/KDE/kdesdk/build.debug/okteta.kf5/libs/kasten/core/tests/..
-I/home/koder/Kode/kdegit/KDE/kdesdk/okteta.kf5/libs/kasten/core/tests/../.. -
I/home/koder/Kode/kdegit/KDE/kdesdk/okteta.kf5/libs/kasten/core/tests/.. -
isystem /home/koder/Kode/qt/qt5/qtbase/include -isystem
/home/koder/Kode/qt/qt5/qtbase/include/QtCore -isystem
/home/koder/Kode/qt/qt5/qtbase/mkspecs/linux-g++ -
I/home/koder/System/kf5/include/KF5/KI18n -I/home/koder/System/kf5/include/KF5
-I/home/koder/System/kf5/include/KF5/KCoreAddons-o
CMakeFiles/kastencoretestio.dir/testdocumentfileloadthread.cpp.o -c
/home/koder/Kode/kdegit/KDE/kdesdk/okteta.kf5/libs/kasten/core/tests/testdocumentfileloadthread.cpp
It is especially strange because with other libs that also include
KLocalizedString there is no problem before in the same build. E.g. oktetacore
has in core/CMakeLists.txt:
--- 8 ---
add_library( ${oktetacore_LIB} SHARED ${oktetacore_LIB_OBJS} )
target_link_libraries( ${oktetacore_LIB} LINK_PUBLIC Qt5::Core )
target_link_libraries( ${oktetacore_LIB} LINK_PRIVATE
KF5::I18n
KF5::KDE4Support
KF5::Codecs #needed for codecs
)
--- 8 ---
and you can see in the log
--- 8 ---
13:23:20 [ 24%] Built target oktetacore
--- 8 ---
What could be different on the buildserver? What is wrong in the
CMakeLists.txt perhaps?
And does Okteta (branch: kf5-port) build for you locally?
Cheers
Friedrich
___
Kde-frameworks-devel mailing list
Kde-frameworks-devel@kde.org
https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
Re: KF5 include problems on the build.kde.org?
Hi,
I am currently struggling to have the KF5 port of Okteta not only build
locally (what it does fine), but also on KDE's build server:
could anybody hint to me why on the build server the file KLocalizedString is
not found for include on building of the static lib kastencoretestio:
I have similar problems with kate on build.kde.org, here it builds, locally,
with a fresh usr/build/src dir,
there it fails unable to find KXMLGUIClient header.
http://build.kde.org/view/Unstable/job/kate_frameworks_qt5/90/console
From http://build.kde.org/job/okteta_master_qt5/8/console :
--- 8 ---
13:23:17
/srv/jenkins/workspace/okteta_master_qt5/libs/kasten/core/tests/testdocumentfileloadthread.cpp:28:28:
fatal error: KLocalizedString: No such file or directory
--- 8 ---
libs/kasten/core/tests/CMakeLists.txt has this:
--- 8 ---
set( kastencoretestio_LIB_SRCS
testdocumentfileloadthread.cpp
[...]
)
add_library( kastencoretestio STATIC ${kastencoretestio_LIB_SRCS} )
target_link_libraries( kastencoretestio LINK_PUBLIC Qt5::Core )
target_link_libraries( kastencoretestio LINK_PRIVATE KF5::I18n
KF5::CoreAddons
Qt5::Core )
--- 8 ---
Locally I see no problem with the problem, and the setup seems proper:
The file KLocalizedString is inside the KI18n include dir as expected, and
also the KDE4 variant is outside the used includes dirs.
$ ls /home/koder/System/kf5/include/KF5/KI18n
ki18n_export.h KLocalizedString klocalizedstring.h KuitMarkup
kuitmarkup.h
KuitSetup kuitsetup.h
$ find /usr/include/ -name KLocalizedString
/usr/include/KDE/KLocalizedString
$ VERBOSE=1 make
[ 0%] Building CXX object
libs/kasten/core/tests/CMakeFiles/kastencoretestio.dir/testdocumentfileloadthread.cpp.o
cd
/home/koder/Kode/kdegit/KDE/kdesdk/build.debug/okteta.kf5/libs/kasten/core/tests
/usr/bin/c++ -DKCOREADDONS_LIB -DQT_CORE_LIB -
DQT_DISABLE_DEPRECATED_BEFORE=0 -DQT_NO_CAST_FROM_ASCII -
DQT_NO_CAST_FROM_BYTEARRAY -DQT_NO_CAST_TO_ASCII -DQT_USE_QSTRINGBUILDER -
D_BSD_SOURCE -D_GNU_SOURCE -D_LARGEFILE64_SOURCE -D_XOPEN_SOURCE=500 -
std=c++0x -Wnon-virtual-dtor -Wno-long-long -Wundef -Wcast-align -Wchar-
subscripts -Wall -W -Wpointer-arith -Wformat-security -fno-exceptions -
DQT_NO_EXCEPTIONS -fno-check-new -fno-common -Woverloaded-virtual -
Werror=return-type -fvisibility=hidden -fvisibility-inlines-hidden -Wall -
std=c++0x -fno-rtti -g3 -fno-inline -fPIC -
I/home/koder/Kode/kdegit/KDE/kdesdk/build.debug/okteta.kf5/libs/kasten/core/tests
-I/home/koder/Kode/kdegit/KDE/kdesdk/okteta.kf5/libs/kasten/core/tests -
I/home/koder/Kode/kdegit/KDE/kdesdk/okteta.kf5/libs/kasten/core/entity -
I/home/koder/Kode/kdegit/KDE/kdesdk/okteta.kf5/libs/kasten/core/document -
I/home/koder/Kode/kdegit/KDE/kdesdk/okteta.kf5/libs/kasten/core/io -
I/home/koder/Kode/kdegit/KDE/kdesdk/okteta.kf5/libs/kasten/core/io/filesystem
-I/home/koder/Kode/kdegit/KDE/kdesdk/okteta.kf5/libs/kasten/core/system -
I/home/koder/Kode/kdegit/KDE/kdesdk/build.debug/okteta.kf5/libs/kasten/core/tests/..
-I/home/koder/Kode/kdegit/KDE/kdesdk/okteta.kf5/libs/kasten/core/tests/../..
-
I/home/koder/Kode/kdegit/KDE/kdesdk/okteta.kf5/libs/kasten/core/tests/.. -
isystem /home/koder/Kode/qt/qt5/qtbase/include -isystem
/home/koder/Kode/qt/qt5/qtbase/include/QtCore -isystem
/home/koder/Kode/qt/qt5/qtbase/mkspecs/linux-g++ -
I/home/koder/System/kf5/include/KF5/KI18n
-I/home/koder/System/kf5/include/KF5
-I/home/koder/System/kf5/include/KF5/KCoreAddons-o
CMakeFiles/kastencoretestio.dir/testdocumentfileloadthread.cpp.o -c
/home/koder/Kode/kdegit/KDE/kdesdk/okteta.kf5/libs/kasten/core/tests/testdocumentfileloadthread.cpp
It is especially strange because with other libs that also include
KLocalizedString there is no problem before in the same build. E.g.
oktetacore
has in core/CMakeLists.txt:
--- 8 ---
add_library( ${oktetacore_LIB} SHARED ${oktetacore_LIB_OBJS} )
target_link_libraries( ${oktetacore_LIB} LINK_PUBLIC Qt5::Core )
target_link_libraries( ${oktetacore_LIB} LINK_PRIVATE
KF5::I18n
KF5::KDE4Support
KF5::Codecs #needed for codecs
)
--- 8 ---
and you can see in the log
--- 8 ---
13:23:20 [ 24%] Built target oktetacore
--- 8 ---
What could be different on the buildserver? What is wrong in the
CMakeLists.txt perhaps?
And does Okteta (branch: kf5-port) build for you locally?
Cheers
Friedrich
___
Kde-frameworks-devel mailing list
Kde-frameworks-devel@kde.org
https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
--
- Dr.-Ing. Christoph Cullmann -
AbsInt Angewandte Informatik GmbH Email: cullm...@absint.com
Science Park 1 Tel: +49-681-38360-22
66123 Saarbrücken Fax: +49-681-38360-20
GERMANYWWW: http://www.AbsInt.com
Re: KF5 include problems on the build.kde.org?
On Saturday 04 January 2014 15:04:58 Friedrich W. H. Kossebau wrote: Hi, I am currently struggling to have the KF5 port of Okteta not only build locally (what it does fine), but also on KDE's build server: could anybody hint to me why on the build server the file KLocalizedString is not found for include on building of the static lib kastencoretestio: From http://build.kde.org/job/okteta_master_qt5/8/console : What strikes me there is: 13:22:15 == Build Dependencies: 13:22:15 kdelibs - Branch frameworks That should be the single frameworks I guess, e.g. on kde-workspace it looks like: == Build Dependencies: cmake - Branch master kparts - Branch master kidletime - Branch master sonnet - Branch master extra-cmake-modules - Branch master kwallet-framework - Branch master and so on. Cheers Martin signature.asc Description: This is a digitally signed message part. ___ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
Re: KF5 include problems on the build.kde.org?
On Saturday 04 January 2014 15:09:14 Christoph Cullmann wrote:
Hi,
I am currently struggling to have the KF5 port of Okteta not only build
locally (what it does fine), but also on KDE's build server:
could anybody hint to me why on the build server the file KLocalizedString
is
not found for include on building of the static lib kastencoretestio:
I have similar problems with kate on build.kde.org, here it builds, locally,
with a fresh usr/build/src dir,
there it fails unable to find KXMLGUIClient header.
http://build.kde.org/view/Unstable/job/kate_frameworks_qt5/90/console
Strange. Let me log onto the server (slave1) to see why it fails there.
/srv/jenkins/install/linux/x86_64/g++/kf5-qt5/frameworks/kxmlgui/inst/lib64/cmake/KF5XmlGui/KF5XmlGuiTargets.cmake
does say
set_target_properties(KF5::XmlGui PROPERTIES
INTERFACE_INCLUDE_DIRECTORIES
${_IMPORT_PREFIX}/include/KF5/KXmlGui;${_IMPORT_PREFIX}/include/KF5
INTERFACE_LINK_LIBRARIES
Qt5::DBus;Qt5::Xml;Qt5::Widgets;KF5::ConfigCore;KF5::ConfigWidgets
)
and yet include/KF5/KXmlGui is not in part of the command-line for compiling
ktexteditor.cpp.o
Ah yep, this is why:
target_link_libraries(ktexteditor LINK_PUBLIC KF5::Parts
LINK_PRIVATE KF5::I18n)
- KF5::XmlGui missing.
What I don't understand is that it works locally, -isystem
/d/kde/inst/kde_frameworks/include/KF5/KXmlGui
is part of the command line for ktexteditor.cpp.o
The only difference I can think of is that build.kde.org uses cmake next while
I use cmake master
But that would mean master is better than next, it's able to follow the
dependencies of KF5::KParts,
which include KF5::KXmlGui, and parse their Targets.cmake file? CC'ing
kde-buildsystem,
I'm a bit lost about the mechanisms involved here and why they would work
differently in master and in next.
I'll do a full rebuild with cmake next, just to test.
--
David Faure, fa...@kde.org, http://www.davidfaure.fr
Working on KDE, in particular KDE Frameworks 5
___
Kde-frameworks-devel mailing list
Kde-frameworks-devel@kde.org
https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
Re: KF5 include problems on the build.kde.org?
Am Samstag, 4. Januar 2014, 15:39:52 schrieb Martin Graesslin: On Saturday 04 January 2014 15:04:58 Friedrich W. H. Kossebau wrote: Hi, I am currently struggling to have the KF5 port of Okteta not only build locally (what it does fine), but also on KDE's build server: could anybody hint to me why on the build server the file KLocalizedString is not found for include on building of the static lib kastencoretestio: From http://build.kde.org/job/okteta_master_qt5/8/console : What strikes me there is: 13:22:15 == Build Dependencies: 13:22:15 kdelibs - Branch frameworks That should be the single frameworks I guess, e.g. on kde-workspace it looks like: == Build Dependencies: cmake - Branch master kparts - Branch master kidletime - Branch master sonnet - Branch master extra-cmake-modules - Branch master kwallet-framework - Branch master Good hint possibly. Though strange that the find_package(KF5 [...]) does not fail, it would have guessed some things changed since the frameworks had been just a branch in the kdelibs repo. Ben, could you take a look and see if perhaps the build dependencies of the Okteta KF5 build would need an update to match the new framework repos? Cheers Friedrich ___ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
Re: KF5 include problems on the build.kde.org?
On Saturday 04 January 2014 15:48:39 Friedrich W. H. Kossebau wrote: Am Samstag, 4. Januar 2014, 15:39:52 schrieb Martin Graesslin: On Saturday 04 January 2014 15:04:58 Friedrich W. H. Kossebau wrote: Hi, I am currently struggling to have the KF5 port of Okteta not only build locally (what it does fine), but also on KDE's build server: could anybody hint to me why on the build server the file KLocalizedString is not found for include on building of the static lib kastencoretestio: From http://build.kde.org/job/okteta_master_qt5/8/console : What strikes me there is: 13:22:15 == Build Dependencies: 13:22:15 kdelibs - Branch frameworks That should be the single frameworks I guess, e.g. on kde-workspace it looks like: == Build Dependencies: cmake - Branch master kparts - Branch master kidletime - Branch master sonnet - Branch master extra-cmake-modules - Branch master kwallet-framework - Branch master Good hint possibly. Though strange that the find_package(KF5 [...]) does not fail, it would have guessed some things changed since the frameworks had been just a branch in the kdelibs repo. Ben, could you take a look and see if perhaps the build dependencies of the Okteta KF5 build would need an update to match the new framework repos? I updated kde-build-metadata, let's see if that helps. Using a branch name frameworks instead of making up yet another variant (kf5-port) would have made things a bit simpler and more consistent :) -- David Faure, fa...@kde.org, http://www.davidfaure.fr Working on KDE, in particular KDE Frameworks 5 ___ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
Re: KF5 include problems on the build.kde.org?
On Saturday 04 January 2014 15:37:34 David Faure wrote: I'll do a full rebuild with cmake next, just to test. Built just fine locally. I'm stumped. -- David Faure, fa...@kde.org, http://www.davidfaure.fr Working on KDE, in particular KDE Frameworks 5 ___ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
KDE-wide Animation settings
Hi,
in KDE4 times we had e.g. in KMessageWidget:
if (KGlobalSettings::graphicEffectsLevel()
KGlobalSettings::SimpleAnimationEffects)
{
// do animation
}
Seems this was dependent on the style but read from some config value that was
set through the kcm 'style', clicking Configure next to the oxygen widget
style.
This configure button was not available for all styles.
In KF5, this became:
if (style()-styleHint(QStyle::SH_Widget_Animate, 0, this))
{
// do animation
}
Using the Oxygen style, this currently returns false. The configure button
only launches an error message saying
There was an error loading the configuration dialog for this style: Unknown
error.
At the same time, I get this output on the console:
kcmshell5(13712)/(default) findLibraryInternal: plugins should not have a
'lib' prefix: libkstyle_oxygen_config.so
The config dialog never shows then.
Is there a way to enable animations so that
style()-styleHint(QStyle::SH_Widget_Animate, 0, this)
returns true?
Greetings,
Dominik
___
Kde-frameworks-devel mailing list
Kde-frameworks-devel@kde.org
https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
KTextEditor Frameworks question
Hi, I cleanup the frameworks branch in kate.git to only have libktexteditor lib and the KTextEditor/ktexteditor includes to be installed as public API. Now, for 5.x, if others port over, like KDevelop, is it a good idea to keep the ktexteditor parts in kate.git, together with the applications, or shall that be split again into a khtml like framework? Greetings Christoph -- - Dr.-Ing. Christoph Cullmann - AbsInt Angewandte Informatik GmbH Email: cullm...@absint.com Science Park 1 Tel: +49-681-38360-22 66123 Saarbrücken Fax: +49-681-38360-20 GERMANYWWW: http://www.AbsInt.com Geschäftsführung: Dr.-Ing. Christian Ferdinand Eingetragen im Handelsregister des Amtsgerichts Saarbrücken, HRB 11234 ___ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
Re: KTextEditor Frameworks question
On Saturday 04 January 2014 19:18:56 Christoph Cullmann wrote: Hi, I cleanup the frameworks branch in kate.git to only have libktexteditor lib and the KTextEditor/ktexteditor includes to be installed as public API. Now, for 5.x, if others port over, like KDevelop, is it a good idea to keep the ktexteditor parts in kate.git, together with the applications, or shall that be split again into a khtml like framework? We want to make separate releases of the 3 major products: frameworks, apps and workspace. So libs that are used by workspace and apps, should be in frameworks. For libs that are only used by apps I guess they can either be in apps or in frameworks. So IMHO the question is: is there a chance the KDE workspace will need it? Of course the other question is: do you want to make it available as a framework for non-KDE developers to use in Qt applications? If the answer is yes to either of these questions, then you need to split it out into a framework. I am not sure if workspace apps will require it, but I doubt it, given an plain text editor is nothing the average application needs, guess only stuff like KDevelop/Kile/... will depend on it. To make the KTextEditor stuff available to a broader developer base would on the other side be nice. What would be required to have the ktexteditor stuff be frameworks ready? Greetings Christoph -- - Dr.-Ing. Christoph Cullmann - AbsInt Angewandte Informatik GmbH Email: cullm...@absint.com Science Park 1 Tel: +49-681-38360-22 66123 Saarbrücken Fax: +49-681-38360-20 GERMANYWWW: http://www.AbsInt.com Geschäftsführung: Dr.-Ing. Christian Ferdinand Eingetragen im Handelsregister des Amtsgerichts Saarbrücken, HRB 11234 ___ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
Re: KDE-wide Animation settings
Hi Dominik,
there are two issues in what you describe
1. There was an error loading the configuration dialog for this style:
Unknown error.
2. QStyle::SH_Widget_Animate
The first problem is that with kf5, the style configuration kcm expects
a libkstyle_oxygen_config.so *plugin* for this configuration, whereas it
was kstyle_oxygen_config.so in kde4 times.
now, as the error message indicates: plugins should not start with lib
and thus, oxygen still installs kstyle_oxygen_config.so only
so that the ill-named plugin is not found, and you get the error dialog.
To fix,
- either we fix the kcm by changing the looked for plugin name (by
removing the lib prefix)
(I think it was added in the first place due to the lack of replacement
for kde4_add_plugin)
- I re-add the lib prefix to the config plugin name installed by oxygen.
I'd vote for the first solution, but this requires kde wide agreement.
For the second issue,
QStyle::SH_Widget_Animate is set to false not in oxygen style but in
KStyle by itself.
This is unrelated to the style configuration.
I am not too inclined to set it to true, since I am absolutely unclear
what this style hint is meant for. Can someone explain ? Notably, I
don't think it should be set to true for _all_ widgets, since most
widgets are already animated internally by oxygen (and thus should not
be by the app), though it indeed should return true for
KMessageWidget, which is not animated internally.
So: should I enable the flag only for widgets that oxygen does not
animate itself ?
Is that the intended purpose of the flag ?
Can someone explain ?
Many thanks in advance,
Hugo
On 01/04/2014 05:58 PM, Dominik Haumann wrote:
Hi,
in KDE4 times we had e.g. in KMessageWidget:
if (KGlobalSettings::graphicEffectsLevel()
KGlobalSettings::SimpleAnimationEffects)
{
// do animation
}
Seems this was dependent on the style but read from some config value that was
set through the kcm 'style', clicking Configure next to the oxygen widget
style.
This configure button was not available for all styles.
In KF5, this became:
if (style()-styleHint(QStyle::SH_Widget_Animate, 0, this))
{
// do animation
}
Using the Oxygen style, this currently returns false. The configure button
only launches an error message saying
There was an error loading the configuration dialog for this style: Unknown
error.
At the same time, I get this output on the console:
kcmshell5(13712)/(default) findLibraryInternal: plugins should not have a 'lib'
prefix: libkstyle_oxygen_config.so
The config dialog never shows then.
Is there a way to enable animations so that
style()-styleHint(QStyle::SH_Widget_Animate, 0, this)
returns true?
Greetings,
Dominik
___
Kde-frameworks-devel mailing list
Kde-frameworks-devel@kde.org
https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
___
Kde-frameworks-devel mailing list
Kde-frameworks-devel@kde.org
https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
Re: KDE-wide Animation settings
On Saturday 04 January 2014 20:19:43 Hugo Pereira Da Costa wrote: The first problem is that with kf5, the style configuration kcm expects a libkstyle_oxygen_config.so *plugin* for this configuration, whereas it was kstyle_oxygen_config.so in kde4 times. now, as the error message indicates: plugins should not start with lib and thus, oxygen still installs kstyle_oxygen_config.so only so that the ill-named plugin is not found, and you get the error dialog. To fix, - either we fix the kcm by changing the looked for plugin name (by removing the lib prefix) Yes. Why does the kcm look for a lib prefix now? Surely there's no good reason for that, the kde4 way was fine. (I think it was added in the first place due to the lack of replacement for kde4_add_plugin) But we can still remove the prefix, can't we? You do so for oxygen :) For the second issue, QStyle::SH_Widget_Animate is set to false not in oxygen style but in KStyle by itself. This is unrelated to the style configuration. I am not too inclined to set it to true, since I am absolutely unclear what this style hint is meant for. Can someone explain ? It should be true on fast local desktops, and false on slow/remote desktops, I suppose. IOW user configurable. Notably, I don't think it should be set to true for _all_ widgets, since most widgets are already animated internally by oxygen (and thus should not be by the app), though it indeed should return true for KMessageWidget, which is not animated internally. So: should I enable the flag only for widgets that oxygen does not animate itself ? No, I think it's rather unrelated. The animations from the widgets themselves are (as can be found by grepping qtbase) - opening trees in QTreeView - moving tabs in QTabBar - dockareas and toolbars Does oxygen animate any of that? I'd be surprised, since these were already animated in Qt4. What's new is letting users turn it off, via kstyle using kconfig. -- David Faure, fa...@kde.org, http://www.davidfaure.fr Working on KDE, in particular KDE Frameworks 5 ___ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
Re: KDE-wide Animation settings
On 01/04/2014 08:52 PM, David Faure wrote: On Saturday 04 January 2014 20:19:43 Hugo Pereira Da Costa wrote: The first problem is that with kf5, the style configuration kcm expects a libkstyle_oxygen_config.so *plugin* for this configuration, whereas it was kstyle_oxygen_config.so in kde4 times. now, as the error message indicates: plugins should not start with lib and thus, oxygen still installs kstyle_oxygen_config.so only so that the ill-named plugin is not found, and you get the error dialog. To fix, - either we fix the kcm by changing the looked for plugin name (by removing the lib prefix) Yes. Why does the kcm look for a lib prefix now? Surely there's no good reason for that, the kde4 way was fine. (I think it was added in the first place due to the lack of replacement for kde4_add_plugin) But we can still remove the prefix, can't we? You do so for oxygen :) yes: add_library(kstyle_oxygen_config MODULE ...) For the second issue, QStyle::SH_Widget_Animate is set to false not in oxygen style but in KStyle by itself. This is unrelated to the style configuration. I am not too inclined to set it to true, since I am absolutely unclear what this style hint is meant for. Can someone explain ? It should be true on fast local desktops, and false on slow/remote desktops, I suppose. IOW user configurable. ok. So this should go to kstyle (nothing oxygen explicit in there). In fact, kstyle returns: KConfigGroup g(KSharedConfig::openConfig(), KDE-Global GUI Settings); return g.readEntry(GraphicEffectsLevel, 0); mmm. No clue which KCM sets this :) (but that answers Dominik's original question I guess) Notably, I don't think it should be set to true for _all_ widgets, since most widgets are already animated internally by oxygen (and thus should not be by the app), though it indeed should return true for KMessageWidget, which is not animated internally. So: should I enable the flag only for widgets that oxygen does not animate itself ? No, I think it's rather unrelated. The animations from the widgets themselves are (as can be found by grepping qtbase) - opening trees in QTreeView - moving tabs in QTabBar - dockareas and toolbars Does oxygen animate any of that? I'd be surprised, since these were already animated in Qt4. What's new is letting users turn it off, via kstyle using kconfig. Nope does not. Thanks for the explanation. ___ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
Re: KDE-wide Animation settings
On Saturday 04 January 2014 20:56:30 Hugo Pereira Da Costa wrote: KConfigGroup g(KSharedConfig::openConfig(), KDE-Global GUI Settings); return g.readEntry(GraphicEffectsLevel, 0); The default value is wrong. In KDE4 it was enabled by default. (see KGlobalSettings::graphicEffectsLevelDefault()) -- David Faure, fa...@kde.org, http://www.davidfaure.fr Working on KDE, in particular KDE Frameworks 5 ___ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
Re: KTextEditor Frameworks question
On Saturday 04 January 2014 19:40:46 Christoph Cullmann wrote: What would be required to have the ktexteditor stuff be frameworks ready? Using all the cmake stuff from other frameworks ;) I just updated and moved the framework template we had in kdelibs to kdeexamples/framework-template. You can use this to generate the entire directory structure if you want. -- David Faure, fa...@kde.org, http://www.davidfaure.fr Working on KDE, in particular KDE Frameworks 5 ___ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
Re: KF5 include problems on the build.kde.org?
On Saturday 04 January 2014 16:53:42 David Faure wrote: On Saturday 04 January 2014 15:37:34 David Faure wrote: I'll do a full rebuild with cmake next, just to test. Built just fine locally. I'm stumped. OK it was a kde-build-metadata/dependency-data configuration issue, it was grabbing the old kdelibs-frameworks stuff. Solving it with Ben now, by having a different dependency-data file for each branch group (i.e. a different one for kf5-qt5 than for the kde4/qt4 stuff). -- David Faure, fa...@kde.org, http://www.davidfaure.fr Working on KDE, in particular KDE Frameworks 5 ___ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
Re: KTextEditor Frameworks question
On Saturday 04 January 2014 19:40:46 Christoph Cullmann wrote: What would be required to have the ktexteditor stuff be frameworks ready? Using all the cmake stuff from other frameworks ;) I just updated and moved the framework template we had in kdelibs to kdeexamples/framework-template. You can use this to generate the entire directory structure if you want. Ok, that shall be not really a problem, given I have already the autotests in the right dir and only ktexteditor = src is needed. Given I have no tests ;) Still, what would be the appropriate way to split the kate.git without loosing the history. Or is the idea for such that it just starts from day zero and history is just in kate.git? Greetings Christoph -- - Dr.-Ing. Christoph Cullmann - AbsInt Angewandte Informatik GmbH Email: cullm...@absint.com Science Park 1 Tel: +49-681-38360-22 66123 Saarbrücken Fax: +49-681-38360-20 GERMANYWWW: http://www.AbsInt.com Geschäftsführung: Dr.-Ing. Christian Ferdinand Eingetragen im Handelsregister des Amtsgerichts Saarbrücken, HRB 11234 ___ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
Re: KTextEditor Frameworks question
On Saturday 04 January 2014 22:40:13 Christoph Cullmann wrote: On Saturday 04 January 2014 19:40:46 Christoph Cullmann wrote: What would be required to have the ktexteditor stuff be frameworks ready? Using all the cmake stuff from other frameworks ;) I just updated and moved the framework template we had in kdelibs to kdeexamples/framework-template. You can use this to generate the entire directory structure if you want. Ok, that shall be not really a problem, given I have already the autotests in the right dir and only ktexteditor = src is needed. This is about the contents of the CMakeLists.txt files too. You should port to ecm_generate_headers if you don't use it yet (you can use my script for that, kde-dev-scripts/kf5/install_forwarding_headers.pl) and compare the cmake stuff with e.g. kcoreaddons or the template. Still, what would be the appropriate way to split the kate.git without loosing the history. Do it just like we did for kdelibs: new repo, old history available via grafting. See kde-dev-scripts/frameworks/split_out_frameworks.sh (change the for loop, obviously - you don't need a loop at all, if you have only one repo to split out). Maybe don't even run the script, just run the commands one by one, to adapt them to your directory structure. Once you have the clean new repo, you'll need to talk to sysadmin for uploading it. -- David Faure, fa...@kde.org, http://www.davidfaure.fr Working on KDE, in particular KDE Frameworks 5 ___ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
Re: KTextEditor Frameworks question
On Saturday 04 January 2014 22:40:13 Christoph Cullmann wrote: On Saturday 04 January 2014 19:40:46 Christoph Cullmann wrote: What would be required to have the ktexteditor stuff be frameworks ready? Using all the cmake stuff from other frameworks ;) I just updated and moved the framework template we had in kdelibs to kdeexamples/framework-template. You can use this to generate the entire directory structure if you want. Ok, that shall be not really a problem, given I have already the autotests in the right dir and only ktexteditor = src is needed. This is about the contents of the CMakeLists.txt files too. You should port to ecm_generate_headers if you don't use it yet (you can use my script for that, kde-dev-scripts/kf5/install_forwarding_headers.pl) and compare the cmake stuff with e.g. kcoreaddons or the template. Yeah, I did notice, we already have stolen most of that tricks in kate.git, including the use of ecm_generate_headers, its only hidden a bit more deep inside the ktexteditor/include structure. Still, what would be the appropriate way to split the kate.git without loosing the history. Do it just like we did for kdelibs: new repo, old history available via grafting. See kde-dev-scripts/frameworks/split_out_frameworks.sh (change the for loop, obviously - you don't need a loop at all, if you have only one repo to split out). Maybe don't even run the script, just run the commands one by one, to adapt them to your directory structure. Once you have the clean new repo, you'll need to talk to sysadmin for uploading it. I see, must then take a look at that ;) Greetings Thanks for all the hints Christoph -- - Dr.-Ing. Christoph Cullmann - AbsInt Angewandte Informatik GmbH Email: cullm...@absint.com Science Park 1 Tel: +49-681-38360-22 66123 Saarbrücken Fax: +49-681-38360-20 GERMANYWWW: http://www.AbsInt.com Geschäftsführung: Dr.-Ing. Christian Ferdinand Eingetragen im Handelsregister des Amtsgerichts Saarbrücken, HRB 11234 ___ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
Re: KDE-wide Animation settings
On Saturday 04 January 2014 20:56:30 Hugo Pereira Da Costa wrote: ok. So this should go to kstyle (nothing oxygen explicit in there). In fact, kstyle returns: KConfigGroup g(KSharedConfig::openConfig(), KDE-Global GUI Settings); return g.readEntry(GraphicEffectsLevel, 0); mmm. No clue which KCM sets this :) (but that answers Dominik's original question I guess) Yes, that answers my question. In particular, using the code widget-style()-styleHint(QStyle::SH_Widget_Animate, 0, widget) is correct *if* we use a KStyle based style. What I personally would like more is to always be able to read this. I of course can use a KSharedConfig::openConfig() and then read the config value myself. However, would it be of interest to have a static accessor for this? Downside is that there are quite a lot of kdeglobals dependent entries... Is the preferred way to read this value manually then in KatePart? Would that also be the preferred way in KMessageWidget? Another issue we have in Kate code: kdeglobals right now do not have this effects enabled by default. A unit test from kde4 times now fails in kf5, because the timings are different, because the effects are off. Are there plans to have a kdeglobals that has enabled effects? Greetings, Dominik ___ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
Re: KDE-wide Animation settings
On Saturday 04 January 2014 23:02:35 Dominik Haumann wrote: On Saturday 04 January 2014 20:56:30 Hugo Pereira Da Costa wrote: ok. So this should go to kstyle (nothing oxygen explicit in there). In fact, kstyle returns: KConfigGroup g(KSharedConfig::openConfig(), KDE-Global GUI Settings); return g.readEntry(GraphicEffectsLevel, 0); mmm. No clue which KCM sets this :) (but that answers Dominik's original question I guess) Yes, that answers my question. In particular, using the code widget-style()-styleHint(QStyle::SH_Widget_Animate, 0, widget) is correct *if* we use a KStyle based style. No, it's correct in all cases :) With the other Qt styles you get true, which is the correct default value. What I personally would like more is to always be able to read this. I of course can use a KSharedConfig::openConfig() and then read the config value myself. However, would it be of interest to have a static accessor for this? Downside is that there are quite a lot of kdeglobals dependent entries... Is the preferred way to read this value manually then in KatePart? Would that also be the preferred way in KMessageWidget? I don't really see what the issue is. Do you care that much for Windows users to be able to turn animations off? Another issue we have in Kate code: kdeglobals right now do not have this effects enabled by default. A unit test from kde4 times now fails in kf5, because the timings are different, because the effects are off. Are there plans to have a kdeglobals that has enabled effects? As I said, it's a bug in the readEntry() call above. The default is supposed to be 1, so you don't need a special kdeglobals. -- David Faure, fa...@kde.org, http://www.davidfaure.fr Working on KDE, in particular KDE Frameworks 5 ___ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
Re: KDE-wide Animation settings
On Saturday 04 January 2014 23:11:14 David Faure wrote: On Saturday 04 January 2014 23:02:35 Dominik Haumann wrote: On Saturday 04 January 2014 20:56:30 Hugo Pereira Da Costa wrote: ok. So this should go to kstyle (nothing oxygen explicit in there). In fact, kstyle returns: KConfigGroup g(KSharedConfig::openConfig(), KDE-Global GUI Settings); return g.readEntry(GraphicEffectsLevel, 0); mmm. No clue which KCM sets this :) (but that answers Dominik's original question I guess) Yes, that answers my question. In particular, using the code widget-style()-styleHint(QStyle::SH_Widget_Animate, 0, widget) is correct *if* we use a KStyle based style. No, it's correct in all cases :) With the other Qt styles you get true, which is the correct default value. Ok, I missed this one, thanks for the clarification! What I personally would like more is to always be able to read this. I of course can use a KSharedConfig::openConfig() and then read the config value myself. However, would it be of interest to have a static accessor for this? Downside is that there are quite a lot of kdeglobals dependent entries... Is the preferred way to read this value manually then in KatePart? Would that also be the preferred way in KMessageWidget? I don't really see what the issue is. Do you care that much for Windows users to be able to turn animations off? Nevermind, was a misunderstanding then. Another issue we have in Kate code: kdeglobals right now do not have this effects enabled by default. A unit test from kde4 times now fails in kf5, because the timings are different, because the effects are off. Are there plans to have a kdeglobals that has enabled effects? As I said, it's a bug in the readEntry() call above. The default is supposed to be 1, so you don't need a special kdeglobals. Ok, so who is going to fix it? ;) Hugo? Greetings, Dominik ___ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
Re: KDE-wide Animation settings
2014/1/4 David Faure fa...@kde.org: On Saturday 04 January 2014 23:02:35 Dominik Haumann wrote: What I personally would like more is to always be able to read this. I of course can use a KSharedConfig::openConfig() and then read the config value myself. However, would it be of interest to have a static accessor for this? Downside is that there are quite a lot of kdeglobals dependent entries... Is the preferred way to read this value manually then in KatePart? Would that also be the preferred way in KMessageWidget? I don't really see what the issue is. Do you care that much for Windows users to be able to turn animations off? Ideally on Windows we'd follow Windows settings rather than KDE apps having their own configuration. SystemParametersInfo(SPI_GETCLIENTAREAANIMATION) seems to get what we'd want. -- Nicolás ___ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
Build failed in Jenkins: plasma-framework_master_qt5 #1037
See http://build.kde.org/job/plasma-framework_master_qt5/1037/changes Changes: [sebas] Adapt to API changes in ThreadWeaver -- Started by remote host 127.0.0.1 with note: Triggered by commit Building remotely on LinuxSlave - 3 in workspace http://build.kde.org/job/plasma-framework_master_qt5/ws/ Running Prebuild steps [plasma-framework_master_qt5] $ /bin/sh -xe /tmp/hudson6922085756554838842.sh + /home/jenkins/scripts/setup-env.sh Preparing to perform KDE Continuous Integration build == Setting Up Sources From git://anongit.kde.org/plasma-framework 6b02b02..160e97c master - origin/master Branch jenkins set up to track remote branch master from origin. == Cleaning Source Tree HEAD is now at 6b02b02 Restore attaching qml debugger Removing build/ Removing install/ Success build forhudson.tasks.Shell@370796f6 Fetching changes from the remote Git repository Fetching upstream changes from git://anongit.kde.org/plasma-framework.git Checking out Revision 160e97cbbae29140f580ea793c92602a4d4b9e8b (refs/heads/jenkins) [plasma-framework_master_qt5] $ /bin/sh -xe /tmp/hudson7596428194051708682.sh + /home/jenkins/scripts/execute-job.sh KDE Continuous Integration Build == Building Project: plasma-framework - Branch master == Build Dependencies: kauth - Branch master kbookmarks - Branch master kdesupport-svn - Branch master kcompletion - Branch master kxmlgui - Branch master solid - Branch master kcoreaddons - Branch master kinit - Branch master kparts - Branch master khtml - Branch master kconfig - Branch master kio - Branch master kcodecs - Branch master extra-cmake-modules - Branch master kactivities - Branch frameworks kdbusaddons - Branch master kcmutils - Branch master kconfigwidgets - Branch master kwindowsystem - Branch master kcrash - Branch master knewstuff - Branch master qt5 - Branch stable kdoctools - Branch master karchive - Branch master sonnet - Branch master cmake - Branch master kservice - Branch master kde4support - Branch master kitemmodels - Branch master kross - Branch master kded - Branch master kjobwidgets - Branch master kdeclarative - Branch master kf5umbrella - Branch master kwallet-framework - Branch master ki18n - Branch master ktextwidgets - Branch master attica - Branch master kjs - Branch master kglobalaccel - Branch master kdnssd-framework - Branch master knotifications - Branch master kiconthemes - Branch master kprintutils - Branch master threadweaver - Branch master kguiaddons - Branch master kdesignerplugin - Branch master kidletime - Branch master == Applying Patches === No patches to apply == Syncing Dependencies from Master Server == Configuring Build -- The C compiler identification is GNU 4.7.2 -- The CXX compiler identification is GNU 4.7.2 -- Check for working C compiler: /home/jenkins/bin/cc -- Check for working C compiler: /home/jenkins/bin/cc -- works -- Detecting C compiler ABI info -- Detecting C compiler ABI info - done -- Check for working CXX compiler: /home/jenkins/bin/c++ -- Check for working CXX compiler: /home/jenkins/bin/c++ -- works -- Detecting CXX compiler ABI info -- Detecting CXX compiler ABI info - done -- Performing Test __KDE_HAVE_W_OVERLOADED_VIRTUAL -- Performing Test __KDE_HAVE_W_OVERLOADED_VIRTUAL - Success -- Performing Test COMPILER_HAS_HIDDEN_VISIBILITY -- Performing Test COMPILER_HAS_HIDDEN_VISIBILITY - Success -- Performing Test COMPILER_HAS_HIDDEN_INLINE_VISIBILITY -- Performing Test COMPILER_HAS_HIDDEN_INLINE_VISIBILITY - Success -- Performing Test COMPILER_HAS_DEPRECATED_ATTR -- Performing Test COMPILER_HAS_DEPRECATED_ATTR - Success CMake Error at /srv/jenkins/install/linux/x86_64/g++/kf5-qt5/frameworks/kf5umbrella/inst/lib64/cmake/KF5/KF5Config.cmake:26 (find_package): Could not find a package configuration file provided by KF5WidgetsAddons with any of the following names: KF5WidgetsAddonsConfig.cmake kf5widgetsaddons-config.cmake Add the installation prefix of KF5WidgetsAddons to CMAKE_PREFIX_PATH or set KF5WidgetsAddons_DIR to a directory containing one of the above files. If KF5WidgetsAddons provides a separate development package or SDK, be sure it has been installed. Call Stack (most recent call first): CMakeLists.txt:45 (find_package) -- Configuring incomplete, errors occurred! See also http://build.kde.org/job/plasma-framework_master_qt5/ws/build/CMakeFiles/CMakeOutput.log;. Configure step exited with non-zero code, assuming failure to configure for project plasma-framework. Build step 'Execute shell' marked build as failure [WARNINGS] Skipping publisher since build result is FAILURE Skipping Cobertura coverage report as build was not UNSTABLE or better ... Recording test results
Build failed in Jenkins: plasma-framework_master_qt5 #1038
See http://build.kde.org/job/plasma-framework_master_qt5/1038/changes Changes: [sebas] Add test for PlasmaCore.ToolTip.target property [sebas] Improve PlasmaCore.ToolTip -- Started by remote host 127.0.0.1 with note: Triggered by commit Building remotely on LinuxSlave - 3 in workspace http://build.kde.org/job/plasma-framework_master_qt5/ws/ Running Prebuild steps [plasma-framework_master_qt5] $ /bin/sh -xe /tmp/hudson8341182582574067078.sh + /home/jenkins/scripts/setup-env.sh Preparing to perform KDE Continuous Integration build == Setting Up Sources From git://anongit.kde.org/plasma-framework 160e97c..8c797fc master - origin/master Branch jenkins set up to track remote branch master from origin. == Cleaning Source Tree HEAD is now at 160e97c Adapt to API changes in ThreadWeaver Removing build/ Success build forhudson.tasks.Shell@370796f6 Fetching changes from the remote Git repository Fetching upstream changes from git://anongit.kde.org/plasma-framework.git Checking out Revision 8c797fce423fda59b13b6a2d53377d10c22f7e38 (refs/heads/jenkins) [plasma-framework_master_qt5] $ /bin/sh -xe /tmp/hudson8332519980482526159.sh + /home/jenkins/scripts/execute-job.sh KDE Continuous Integration Build == Building Project: plasma-framework - Branch master == Build Dependencies: kauth - Branch master kidletime - Branch master kjs - Branch master kdesupport-svn - Branch master kcompletion - Branch master kbookmarks - Branch master kinit - Branch master kparts - Branch master khtml - Branch master knotifications - Branch master kconfig - Branch master kcrash - Branch master kcodecs - Branch master extra-cmake-modules - Branch master kactivities - Branch frameworks kdbusaddons - Branch master kcmutils - Branch master kwindowsystem - Branch master attica - Branch master knewstuff - Branch master qt5 - Branch stable kde4support - Branch master karchive - Branch master sonnet - Branch master cmake - Branch master kio - Branch master kservice - Branch master kxmlgui - Branch master kitemmodels - Branch master kross - Branch master kded - Branch master kglobalaccel - Branch master kdeclarative - Branch master threadweaver - Branch master kconfigwidgets - Branch master ki18n - Branch master solid - Branch master ktextwidgets - Branch master kdoctools - Branch master kjobwidgets - Branch master kcoreaddons - Branch master kdnssd-framework - Branch master kwallet-framework - Branch master kf5umbrella - Branch master kiconthemes - Branch master kguiaddons - Branch master kprintutils - Branch master kdesignerplugin - Branch master == Applying Patches === No patches to apply == Syncing Dependencies from Master Server == Configuring Build -- The C compiler identification is GNU 4.7.2 -- The CXX compiler identification is GNU 4.7.2 -- Check for working C compiler: /home/jenkins/bin/cc -- Check for working C compiler: /home/jenkins/bin/cc -- works -- Detecting C compiler ABI info -- Detecting C compiler ABI info - done -- Check for working CXX compiler: /home/jenkins/bin/c++ -- Check for working CXX compiler: /home/jenkins/bin/c++ -- works -- Detecting CXX compiler ABI info -- Detecting CXX compiler ABI info - done -- Performing Test __KDE_HAVE_W_OVERLOADED_VIRTUAL -- Performing Test __KDE_HAVE_W_OVERLOADED_VIRTUAL - Success -- Performing Test COMPILER_HAS_HIDDEN_VISIBILITY -- Performing Test COMPILER_HAS_HIDDEN_VISIBILITY - Success -- Performing Test COMPILER_HAS_HIDDEN_INLINE_VISIBILITY -- Performing Test COMPILER_HAS_HIDDEN_INLINE_VISIBILITY - Success -- Performing Test COMPILER_HAS_DEPRECATED_ATTR -- Performing Test COMPILER_HAS_DEPRECATED_ATTR - Success CMake Error at /srv/jenkins/install/linux/x86_64/g++/kf5-qt5/frameworks/kf5umbrella/inst/lib64/cmake/KF5/KF5Config.cmake:26 (find_package): Could not find a package configuration file provided by KF5WidgetsAddons with any of the following names: KF5WidgetsAddonsConfig.cmake kf5widgetsaddons-config.cmake Add the installation prefix of KF5WidgetsAddons to CMAKE_PREFIX_PATH or set KF5WidgetsAddons_DIR to a directory containing one of the above files. If KF5WidgetsAddons provides a separate development package or SDK, be sure it has been installed. Call Stack (most recent call first): CMakeLists.txt:45 (find_package) -- Configuring incomplete, errors occurred! See also http://build.kde.org/job/plasma-framework_master_qt5/ws/build/CMakeFiles/CMakeOutput.log;. Configure step exited with non-zero code, assuming failure to configure for project plasma-framework. Build step 'Execute shell' marked build as failure [WARNINGS] Skipping publisher since build result is FAILURE Skipping Cobertura coverage report as build was not UNSTABLE or better ... Recording test
Build failed in Jenkins: plasma-framework_master_qt5 #1039
See http://build.kde.org/job/plasma-framework_master_qt5/1039/changes Changes: [scripty] SVN_SILENT made messages (.desktop file) -- Started by remote host 127.0.0.1 with note: Triggered by commit Building remotely on LinuxSlave - 3 in workspace http://build.kde.org/job/plasma-framework_master_qt5/ws/ Running Prebuild steps [plasma-framework_master_qt5] $ /bin/sh -xe /tmp/hudson8843237683327234490.sh + /home/jenkins/scripts/setup-env.sh Preparing to perform KDE Continuous Integration build == Setting Up Sources From git://anongit.kde.org/plasma-framework 8c797fc..4441ba4 master - origin/master Branch jenkins set up to track remote branch master from origin. == Cleaning Source Tree HEAD is now at 8c797fc Improve PlasmaCore.ToolTip Removing build/ Success build forhudson.tasks.Shell@370796f6 Fetching changes from the remote Git repository Fetching upstream changes from git://anongit.kde.org/plasma-framework.git Checking out Revision 4441ba40955f24e909b7435b5af1f1e1ed714414 (refs/heads/jenkins) [plasma-framework_master_qt5] $ /bin/sh -xe /tmp/hudson8728763871559033433.sh + /home/jenkins/scripts/execute-job.sh KDE Continuous Integration Build == Building Project: plasma-framework - Branch master == Build Dependencies: kauth - Branch master kf5umbrella - Branch master extra-cmake-modules - Branch master kjobwidgets - Branch master kcompletion - Branch master kdoctools - Branch master kcmutils - Branch master kparts - Branch master kconfig - Branch master khtml - Branch master kcrash - Branch master kcodecs - Branch master kidletime - Branch master kactivities - Branch frameworks kdbusaddons - Branch master kbookmarks - Branch master kross - Branch master kinit - Branch master karchive - Branch master kwindowsystem - Branch master attica - Branch master knewstuff - Branch master qt5 - Branch stable kdesupport-svn - Branch master kjs - Branch master kwallet-framework - Branch master cmake - Branch master kservice - Branch master kde4support - Branch master knotifications - Branch master kitemmodels - Branch master ki18n - Branch master kdeclarative - Branch master kglobalaccel - Branch master kded - Branch master kxmlgui - Branch master threadweaver - Branch master kconfigwidgets - Branch master kio - Branch master kprintutils - Branch master solid - Branch master ktextwidgets - Branch master kcoreaddons - Branch master kdnssd-framework - Branch master kiconthemes - Branch master sonnet - Branch master kguiaddons - Branch master kdesignerplugin - Branch master == Applying Patches === No patches to apply == Syncing Dependencies from Master Server == Configuring Build -- The C compiler identification is GNU 4.7.2 -- The CXX compiler identification is GNU 4.7.2 -- Check for working C compiler: /home/jenkins/bin/cc -- Check for working C compiler: /home/jenkins/bin/cc -- works -- Detecting C compiler ABI info -- Detecting C compiler ABI info - done -- Check for working CXX compiler: /home/jenkins/bin/c++ -- Check for working CXX compiler: /home/jenkins/bin/c++ -- works -- Detecting CXX compiler ABI info -- Detecting CXX compiler ABI info - done -- Performing Test __KDE_HAVE_W_OVERLOADED_VIRTUAL -- Performing Test __KDE_HAVE_W_OVERLOADED_VIRTUAL - Success -- Performing Test COMPILER_HAS_HIDDEN_VISIBILITY -- Performing Test COMPILER_HAS_HIDDEN_VISIBILITY - Success -- Performing Test COMPILER_HAS_HIDDEN_INLINE_VISIBILITY -- Performing Test COMPILER_HAS_HIDDEN_INLINE_VISIBILITY - Success -- Performing Test COMPILER_HAS_DEPRECATED_ATTR -- Performing Test COMPILER_HAS_DEPRECATED_ATTR - Success CMake Error at /srv/jenkins/install/linux/x86_64/g++/kf5-qt5/frameworks/kf5umbrella/inst/lib64/cmake/KF5/KF5Config.cmake:26 (find_package): Could not find a package configuration file provided by KF5WidgetsAddons with any of the following names: KF5WidgetsAddonsConfig.cmake kf5widgetsaddons-config.cmake Add the installation prefix of KF5WidgetsAddons to CMAKE_PREFIX_PATH or set KF5WidgetsAddons_DIR to a directory containing one of the above files. If KF5WidgetsAddons provides a separate development package or SDK, be sure it has been installed. Call Stack (most recent call first): CMakeLists.txt:45 (find_package) -- Configuring incomplete, errors occurred! See also http://build.kde.org/job/plasma-framework_master_qt5/ws/build/CMakeFiles/CMakeOutput.log;. Configure step exited with non-zero code, assuming failure to configure for project plasma-framework. Build step 'Execute shell' marked build as failure [WARNINGS] Skipping publisher since build result is FAILURE Skipping Cobertura coverage report as build was not UNSTABLE or better ... Recording test results
