On May 24, 5:54 pm, "Christopher Anderson" <[EMAIL PROTECTED]>
wrote:
> > Debug builds are incompatible with release builds. You'll need to
> > build every binary extension in debug mode (assuming the original
> > authors don't provide debug builds).
>
> Right, and this is what I would like to avo
> Debug builds are incompatible with release builds. You'll need to
> build every binary extension in debug mode (assuming the original
> authors don't provide debug builds).
Right, and this is what I would like to avoid having to do.
Thanks,
Chris
PS. Sorry for the duplicate olsongt
--
http:/
>
> I've tried compiling python from source, and my extension module,
> using MSVC8 (free express version), and I managed to get this to work.
> The thing is, I don't want to have to recompile every single python
> package I need (wxPython, SciPy, etc).
>
Debug builds are incompatible with releas
On Tue, 22 May 2007 18:49:04 -0700, "Christopher Anderson"
<[EMAIL PROTECTED]> wrote:
>problem is, when I attempt to use it, I get a segfault. Now, I'm
>pretty sure this segfault is just a bug in my C++ code. So of course,
>I would like to debug this thing somehow. I tried using the mingw gdb
>giv
> I am trying to build an extension module written in C++ on windows XP.
> I am trying to use only open-source tools, such as mingw. I'm using
> the Python 2.5 official, and it seems to compile my module just fine
> (I'm using the --compiler=mingw32). I can also import the module. The
> problem is,
Hello all. I have a fairly fundamental question that I have been
googling like crazy, but I can only seem to find really outdated or
unreliable info:
I am trying to build an extension module written in C++ on windows XP.
I am trying to use only open-source tools, such as mingw. I'm using
the Pytho
