On Thursday 07 May 2009 10:17:14 Mark Purcell wrote: > On Wednesday 06 May 2009 22:20:55 Tom Albers wrote: > > I thought debian released packages without debug output? > > Tom, > > The Debian packages are built with standard cmake calls: > https://buildd.debian.org/fetch.cgi?pkg=rsibreak;ver=1:0.9.0-4;arch=hppa;st >amp=1240107416 > > Should we be setting some flags to disable debug output?
we are building with approximately relwithdebinfo flags. More precisely, we have built with -g -O2 -DNDEBUG Quite recently, kde has added -DQT_NO_DEBUG to the flags used - and we will probably follow some time over the summer. This still enables the kDebug() calls, but we have all debug areas disabled by default. So basically, it depends on how rsibreak outputs things. if it uses qDebug(), this will be fixed (by kdelibs and a rsibreak rebuild) during the summer if it uses kDebug() without specifying debug areas (kDebug(1234)), we will output it and I would consider rsibreak slightly broken here. If this is the case, a debug area should be requested and rsibreak should use it for its kDebug calls. if it uses its own logging mechanism (which I doubt), it would also be a fix in rsibreak. /Sune -- I cannot install on a secret password, how does it work? You should ping the connector over a submenu of a IRC bus of the wordprocessor over a 3D firewall.
Description: This is a digitally signed message part.
_______________________________________________ pkg-kde-extras mailing list firstname.lastname@example.org http://lists.alioth.debian.org/mailman/listinfo/pkg-kde-extras