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
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
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
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
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
[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
---
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:
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/121213/#review70796
---
kdecore/io/kdebug.cpp
On Nov. 23, 2014, 12:20 a.m., Thomas Lübking wrote:
kdecore/io/kdebug.cpp, line 717
https://git.reviewboard.kde.org/r/121213/diff/1/?file=329504#file329504line717
Why do you need to sharpen the match?
Because otherwise the symbol to be demangled is left with a trailing space,
On Nov. 22, 2014, 11:20 nachm., Thomas Lübking wrote:
kdecore/io/kdebug.cpp, line 717
https://git.reviewboard.kde.org/r/121213/diff/1/?file=329504#file329504line717
Why do you need to sharpen the match?
René J.V. Bertin wrote:
Because otherwise the symbol to be demangled is
On Nov. 23, 2014, 12:20 a.m., Thomas Lübking wrote:
kdecore/io/kdebug.cpp, line 717
https://git.reviewboard.kde.org/r/121213/diff/1/?file=329504#file329504line717
Why do you need to sharpen the match?
René J.V. Bertin wrote:
Because otherwise the symbol to be demangled is
On Nov. 22, 2014, 11:20 nachm., Thomas Lübking wrote:
kdecore/io/kdebug.cpp, line 717
https://git.reviewboard.kde.org/r/121213/diff/1/?file=329504#file329504line717
Why do you need to sharpen the match?
René J.V. Bertin wrote:
Because otherwise the symbol to be demangled is
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
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. We
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:
~~~+
15 matches
Mail list logo
