Triggering rebuild after changing a *.json file

Hey all, in my quest for better *.json support in KF5 based applications, I noticed that we currently do not rebuild properly on changes to the *.desktop or *.json files. For KDevelop, I'm thus playing around with something like this currently: ~~~+ function(kdevplatform_add_plugin

Re: Q_PLUGIN_METADATA for KDE plugins?

On Sunday 23 November 2014 03:53:57 Milian Wolff wrote: > Hey all, > > do we also need Q_PLUGIN_METADATA for plugins of, say, Kate or KDevelop? > Currently we don't use it and it seems to work fine. Can someone shed some > light on this? Are we missing out on something? Sigh, I'm tired apparently

Q_PLUGIN_METADATA for KDE plugins?

Hey all, do we also need Q_PLUGIN_METADATA for plugins of, say, Kate or KDevelop? Currently we don't use it and it seems to work fine. Can someone shed some light on this? Are we missing out on something? Thanks -- Milian Wolff m...@milianw.de http://milianw.de

Re: Review Request 121213: [OS X] correctly parse backtrace for demangling symbols

> On Nov. 22, 2014, 11:20 nachm., Thomas Lübking wrote: > > kdecore/io/kdebug.cpp, line 717 > > > > > > Why do you need to sharpen the match? > > René J.V. Bertin wrote: > Because otherwise the symbol to be

Re: Review Request 121213: [OS X] correctly parse backtrace for demangling symbols

> On Nov. 23, 2014, 12:20 a.m., Thomas Lübking wrote: > > kdecore/io/kdebug.cpp, line 717 > > > > > > Why do you need to sharpen the match? > > René J.V. Bertin wrote: > Because otherwise the symbol to be de

Re: Review Request 121213: [OS X] correctly parse backtrace for demangling symbols

> On Nov. 22, 2014, 11:20 nachm., Thomas Lübking wrote: > > kdecore/io/kdebug.cpp, line 717 > > > > > > Why do you need to sharpen the match? > > René J.V. Bertin wrote: > Because otherwise the symbol to be

Re: Review Request 121213: [OS X] correctly parse backtrace for demangling symbols

> On Nov. 23, 2014, 12:20 a.m., Thomas Lübking wrote: > > kdecore/io/kdebug.cpp, line 717 > > > > > > Why do you need to sharpen the match? Because otherwise the symbol to be demangled is left with a trailing sp

Re: Review Request 121213: [OS X] correctly parse backtrace for demangling symbols

--- This is an automatically generated e-mail. To reply, visit: https://git.reviewboard.kde.org/r/121213/#review70796 --- kdecore/io/kdebug.cpp

Review Request 121213: [OS X] correctly parse backtrace for demangling symbols

--- This is an automatically generated e-mail. To reply, visit: https://git.reviewboard.kde.org/r/121213/ --- Review request for KDE Software on Mac OS X and kdelibs. Repository: kdel

KDE-CI IRC meeting - Your possible KDE contributions in non-C++

[Disclaimer: this email is sent to kde-devel, kde-core-devel and kde- frameworks-devel. Please just answer to kde-devel!] Morning ladies and gentlemen Oh and please scratch the "please" above ;-). This email is about another possibility to contribute to KDE. It's about taking work off Ben's shou

Adventures in Bodega

Hello list, I realize this list will reach many more people than could probably answer, but the -active list seems to be dead from what I hear, so I thought I'd try here. In looking into bodega as a successor to opendesktop and ocs I've tried to setup a local bodega instance on my machine. The doc

Re: Review Request 121083: Replace manual export files with CMake's generate_export_header

> On Nov. 22, 2014, 12:18 vorm., Harald Sitter wrote: > > This breaks the kde4 build as ECM is not being used there and > > generate_export_header is not available without ECM. > > Andrius da Costa Ribas wrote: > generate_export_header isn't in ECM, but in cmake itself > (http://www.cmake.

Re: Review Request 121083: Replace manual export files with CMake's generate_export_header

> On Nov. 22, 2014, 12:18 a.m., Harald Sitter wrote: > > This breaks the kde4 build as ECM is not being used there and > > generate_export_header is not available without ECM. > > Andrius da Costa Ribas wrote: > generate_export_header isn't in ECM, but in cmake itself > (http://www.cmake.o

Re: Review Request 121083: Replace manual export files with CMake's generate_export_header

> On nov. 22, 2014, 12:18 a.m., Harald Sitter wrote: > > This breaks the kde4 build as ECM is not being used there and > > generate_export_header is not available without ECM. > > Andrius da Costa Ribas wrote: > generate_export_header isn't in ECM, but in cmake itself > (http://www.cmake.o

Re: Review Request 121083: Replace manual export files with CMake's generate_export_header

> On Nov. 22, 2014, 12:18 a.m., Harald Sitter wrote: > > This breaks the kde4 build as ECM is not being used there and > > generate_export_header is not available without ECM. > > Andrius da Costa Ribas wrote: > generate_export_header isn't in ECM, but in cmake itself > (http://www.cmake.o