wx 3 logging excessively...

[Carl Godkin]

Hi,

We're migrating to wx 3.0.0 and running into lots of extra messages.

Apparently wxWidgets 3.0 changed so that __WXDEBUG__ is always set -- even
in release builds -- and we're seeing all sorts of wxLogDebug output in
unexpected places from our applications.

For instance, there's a new wxLogDebug call in the wxGTK setup code
(utilsgtk.cpp, line 225):

wxLogDebug("Failed to connect to session manager: %s", smerr);

which comes up every time for us since we don't run on Linux desktops with
session managers. (In wx 2.8, there was no message here, and it wouldn't
have been printed anyway in release mode.)

I would like our customers (and the rest of us) not to see such messages.

I feel I must be missing something here. Surely no one else wants to see
debug messages in release mode, do they?

Thanks,

carl

[Vadim Zeitlin]

On Mon, 10 Feb 2014 09:52:10 -0800 Carl Godkin wrote:

CG> Apparently wxWidgets 3.0 changed so that __WXDEBUG__ is always set -- even
CG> in release builds

I hoped to have explained it all reasonably clearly in

http://docs.wxwidgets.org/trunk/overview_debugging.html

Did you read it but still have questions or just didn't find this page?

CG> I feel I must be missing something here.

TL;DR: Define NDEBUG for your application release build.

Regards,
VZ

[Carl Godkin]

Great! I never saw that page before. Lots of good information and just
what I need.

Thanks,

carl

Post by Vadim Zeitlin
CG> Apparently wxWidgets 3.0 changed so that __WXDEBUG__ is always set -- even
CG> in release builds
I hoped to have explained it all reasonably clearly in
http://docs.wxwidgets.org/trunk/overview_debugging.html
Did you read it but still have questions or just didn't find this page?
CG> I feel I must be missing something here.
TL;DR: Define NDEBUG for your application release build.
Regards,
VZ
--
TT-Solutions: wxWidgets consultancy and technical support
http://www.tt-solutions.com/