[wxPython] wxGTK Debug Problem

wxPython Users
1

Hi Robin,

On my problem with wxGTK/wxPython debug you suggest:

"The debug and non-debug versions of wxWindows are not
binary compatible, so
you need to rebuild wxPython too. When the
__WXDEBUG__ macro is defined
then many of the classes/methods will have different
signatures etc."

I am using the wxPython2.3.2.1 source rpm. The
'--debug' switch to setup.py appends __WXDEBUG__ to
the defines list. However, with the exception of

./contrib/xrc/contrib/include/wx/xrc/xmlres.h

no source file knows anything of the __WXDEBUG__
macro. In addition the macro is only set up in
defines (in setup.py) where os.name=nt.

The same is true of the source tar file.

Is there a better variant around?

···

__________________________________________________
Do You Yahoo!?
Yahoo! Games - play chess, backgammon, pool and more
http://games.yahoo.com/

2

I am using the wxPython2.3.2.1 source rpm. The
'--debug' switch to setup.py appends __WXDEBUG__ to
the defines list. However, with the exception of

./contrib/xrc/contrib/include/wx/xrc/xmlres.h

no source file knows anything of the __WXDEBUG__
macro. In addition the macro is only set up in
defines (in setup.py) where os.name=nt.

On Unix the __WXDEBUG__ flag comes from wx-config, which setup.py executes
to get the flags and libs specified by the wxWindows build. Try running
"wx-config --cflags" to see if it spits out -D__WXDEBUG__ or not. If not
then you need to build/install the debug version of the wxGTK_devel RPM too.

···

--
Robin Dunn
Software Craftsman
robin@AllDunn.com Java give you jitters?
http://wxPython.org Relax with wxPython!