[C++-sig] [boost.python] Debug build on win32 runtime trouble

David Abrahams dave at boostpro.com
Fri Sep 19 08:16:56 CEST 2008


on Thu Sep 18 2008, Olaf Peter <ope-devel-AT-gmx.de> wrote:

>>> Depency walker shows:
>>>
>>> d:\work\...\build\debug\PYTHON25_D.DLL
>>> d:\work\...\build\debug\BOOST_PYTHON-VC80-MT-GD-1_35.DLL
>>> + c:\windows\system32\PYTHON25.DLL
> [...]
>>> Note the BOOST_DEBUG_PYTHON define. As linker flags I've used:
>
>> To get a pure python-debug build you need to explicitly tell boost to
>> link to the debug version of python, by passing the option
>> python-debugging=on to bjam when building boost. You will ghen get
>> boost_python-vc80-mt-gyd-1_35.lib and .dll instead, and need to link
>> to that.
>>
>> You also need to define BOOST_DEBUG_PYTHON when you build your
>> application, see this url:
>>
> http://www.boost.org/doc/libs/1_36_0/libs/python/doc/building.html#python-debugging-builds
>
> As first thank you for the answer. Anyway, I assume the debug build of
> boost_python dll ist wrong and points to the wrong python25.dll, should be
> python25_d.dll. Could it be? 

No, the build is right, i.e. intentional.  Please read the URL as
suggested by Olaf, it really does explain everything.  Also please
follow the advice in

http://www.boost.org/doc/libs/1_36_0/libs/python/doc/building.html#no-install-quickstart

for people like you who want to use build systems other than bjam.  It
will potentially save you a great deal of pain.

-- 
Dave Abrahams
BoostPro Computing
http://www.boostpro.com



More information about the Cplusplus-sig mailing list