Amebis/wxWidgets
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Merged wxPython 2.2.2 over to the main branch

Browse Source 
git-svn-id: https://svn.wxwidgets.org/svn/wx/wxWidgets/trunk@8658 c3d73ce0-8a6f-49c7-b76d-6d57e0e08775
This commit is contained in:
Robin Dunn
2000-10-30 21:08:42 +00:00
parent 7874bf5430
commit c368d904fc
193 changed files with 21992 additions and 4366 deletions
Download Patch File Download Diff File Expand all files Collapse all files

20
wxPython/distrib/README.dbg.txt
View File

@@ -10,11 +10,21 @@ Another debugging feature is when the wxPython program exits, it will
print to stdout information about any wxWindows C++ objects that
havn't been properly cleaned up.
This archive contains a new wxWindows DLL named wx[version]d.dll that
should be copied to the windows system directory or some other
directory on the PATH.You will also find replacements for all of
wxPython's *.pyd files that are linked to use this DLL. Until I put
together a new installer, you'll need to copy things manually.
This archive contains a new wxWindows DLL named wx[version]d.dll and a
debugging version of the core wxPython module, wxc_d.pyd. These
should be put into your wxPython package directory. Also included are
the debuging version of Python, python_d.exe and python[VER]_d.dll
which can be put wherever you like.
In order to run the debugging version of wxPython sumply run you
program with python_d.exe instead of python.exe. This lets the
debugging version sit side by side with the production version, with
no need for swapping this around. You will also need _d versions of
any other extension modules you are using. If you need _d's for any
of the other standard Python extensions you can get them here, for 2.0
at least:
http://www.pythonlabs.com/products/python2.0/downloads/BeOpen-Python-2.0-Debug.zip
Robin