corrected CodeWarrior project target names and generated application names

[wxWidgets.git] / wxPython / distrib / README.dbg.txt

diff --git a/wxPython/distrib/README.dbg.txt b/wxPython/distrib/README.dbg.txt
index b2289512b394a1f86c8191f19611572feb5ad652..ba829d4443f05e376f54c63c7ea7a8b94ab94ea4 100644 (file)
--- a/wxPython/distrib/README.dbg.txt
+++ b/wxPython/distrib/README.dbg.txt
@@ -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.
 
 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
 
 
 Robin