Re: [Boost-build] Debug Python extension build doesn't select debug Python

Subject: Re: [Boost-build] Debug Python extension build doesn't select debug Python
From: John Reid (j.reid_at_[hidden])
Date: 2011-03-16 09:31:22

On 16/03/11 13:16, John Reid wrote:
> My debug Python extension builds do not seem to select the correct
> python I have built with debugging on.
>
> This is my user-config.jam:
>
> using python ;
> using python : : /home/john/local/python-dbg/bin/python2.7
> :
> :
> : <python-debugging>on
> ;
>
>
>
> I go to $BOOST_ROOT/libs/python/example and do
> bjam -q -j3 debug -d+2
>
> I get a bunch of compilation lines like:
>
> gcc.compile.c++ bin/gcc-4.4.3/debug/python-debugging-on/getting_started1.o
>
> "g++" -ftemplate-depth-128 -O0 -fno-inline -Wall -g -fPIC
> -DBOOST_DEBUG_PYTHON -I"../../.." -I"/usr/include/python2.6" -c -o
> "bin/gcc-4.4.3/debug/python-debugging-on/getting_started1.o"
> "getting_started1.cpp"
>
> where /usr/include/python2.6 is included, not the headers for my python
> 2.7 debug build. I think this used to work, I have recently updated
> boost to the latest svn. Can anyone verify if this has stopped working
> for them also?
>

I should add I added the necessary requirements to the Jamroot for the 
example:

<variant>debug:<python-debugging>on