Thanks for your reply, Mark. I probably wasn't very clear, but I did build a debug version of python. I'll provide more detailed information, as I'm sure the solution to my quandry is very likely a no-brainer for most of the people on this list.
I checked out a copy of the python 2.4.4 source distribution into a directory (c:\temp\Python-2.4.4). Following the instructions in the PCBuild subdirectory, I did a build with the 'debug' solution configuration for pythoncore, python, and the subprojects that built out-of-the-box. The build was successful (no errors or warnings). This created files like 'python24_d.lib' in my c:\temp\Python-2.4.4\Pcbuild\ directory. Next I checked out source files for pywin32-210, and unpacked them into 'c:\temp\pywin32' (thereby creating directories similar to 'c:\temp\pywin32\com', etc.). I'm not exactly sure where these source files should live in order to do the debug build, but I thought as a first guess, I'd put them where other "subprojects" would go. The notes for building Python itself said that "if your Pcbuild is .......\dist\src\Pcbuild\, unpack into new subdirectories of dist\". In my case, the '\dist' would correspond to 'c:\temp'. This project may not be the same thing as other subprojects, but it seemed like a good guess to me. I then tried building the pywin32 extensions with: "python setup.py -q build -debug", and it failed with the error I mentioned. I also tried putting the pywin32 directory under c:\temp\Python-2.4.4, as well as under c:\temp\Python-2.4.4\Pcbuild - neither of these worked either. Do I actually need to install the debug version of python that I built? (I'd prefer not to overwrite my regular python build, but will happily do that if that's what is required). Do I need to set some environment variables? I believe I likely just need to tell the build program for pywin32 where the debug version of python is, but I'm not sure how to do that. Sorry for the long explanation for a very elementary question, but what am I doing wrong? Regards, Gerrat -----Original Message----- From: Mark Hammond [mailto:[EMAIL PROTECTED] Sent: Sunday, July 08, 2007 9:26 PM To: Gerrat Rickert; python-win32@python.org Subject: Re: [python-win32] Trying to build debug version of win32 extensions You also need to build Python itself in debug mode - that creates python_d.* AFAIK, there has been no decision about the official Python 2.6 compiler and VS2003 is still the "official" one for 2.5... Cheers, Mark -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Gerrat Rickert Sent: Saturday, 7 July 2007 7:22 AM To: python-win32@python.org Subject: [python-win32] Trying to build debug version of win32 extensions I'm trying to build a debug version of the win32 extensions (basically to help track down a memory leak in a COM automation program I've written). To that end, I purchased a Visual C++ .Net Deluxe Learning Edition Book (which is probably the cheapest way to get the Visual C++ compiler required). Following the instructions in the source distribution, I was able to build a debug version of python from source (unfortunately, I know very little about C/C++). I checked out the python win32 source files, and am trying to build a debug version of this as well, but I'm not having much success. Though matter where I place the main directory with the win32 source files, it still fails to compile - I get an error: LINK: fatal error LINK1104: cannot open file 'python24_d.lib' [I'm trying to build using: "python setup.py -q build -debug"] This file exists in the directory I compiled the debug version of the main python distribution, but I'm not sure what I need to do so that the setup program can find it. Any help/direction would be appreciated. Thanks, Gerrat _______________________________________________ Python-win32 mailing list Python-win32@python.org http://mail.python.org/mailman/listinfo/python-win32
