[KDE/Mac] chattyness & log pollution

Ian Wadham iandw.au at gmail.com
Sat Aug 2 05:46:46 UTC 2014

Hi everyone,

On 01/08/2014, at 6:55 AM, René J.V. Bertin wrote:
> KDE apps tend to be incredibly chatty on stdout and/or stderr. When they're launched through LaunchServices on OS X, all that output goes into the system log. Is there a way to avoid this from happening? I've tried replacing the bundle executable with a wrapper script that redirects both streams to /dev/null, but incomprehensibly that has no effect.

I think we may have been missing some settings in MacPorts' builds of
KDE and Qt...

Apparently, it is intended by the KDE build-systems guys that CMake
build-types Release and RelWithDebInfo (the default) should build
apps that are, as far as possible, completely silent on stdout and stderr.

That is unless the user decides to turn on some KDebug() messages
by using the KDebugDialog application.

See [1], [2] and the email discussion in [3], from several horses' mouths.

Re silencing output from qDebug() and Q_ASSERT(), see [4] and [5].

FWIW I have not suddenly become all-knowing… :-) … I just stumbled
across this stuff when trying to get to the bottom of what Q_ASSERT()
actually does and how it actually works… :-)

Cheers, Ian W.

[1] https://techbase.kde.org/Development/CMake/Addons_for_KDE#Buildtypes
[2] https://techbase.kde.org/Development/CMake/Addons_for_KDE#Debugging_Features_in_Detail
[3] http://mail.kde.org/pipermail/kde-buildsystem/2009-January/005468.html

[4] http://qt-project.org/doc/qt-5/qtglobal.html#qDebug
[5] http://public.kitware.com/Bug/view.php?id=14292

More information about the kde-mac mailing list