Too late--I managed to get it to build a bit ago. But that being said, I
had read that little blurb while trying to figure out what was going on.
Unfortunately it's the kind of thing that makes sense if you already know
what to do, but it didn't make any sense to me when I was stammering
through
Please read:
http://www.boost.org/doc/libs/1_49_0/libs/python/doc/building.html#python-debugging-builds
HTH,
Dave
on Wed Feb 15 2012, Adam Preble wrote:
> I previously posted about runtime oddness when switching to a debug
> build of python. I figured I needed to rebuild Boost.Python. The
>
If you haven't already, you may need to take this to a Boost.Build list;
I avoid Boost's build system whenever possible, and I know even less
about using it on Windows.
Sorry!
Jim
On 02/15/2012 10:38 AM, Adam Preble wrote:
I previously posted about runtime oddness when switching to a debug
I previously posted about runtime oddness when switching to a debug build
of python. I figured I needed to rebuild Boost.Python. The build process
is fixated on using the normal python.exe and python.lib paths, rather than
python_d.exe and python_d.lib. I have put those files in my Python26
dire
