From: David Abrahams (dave_at_[hidden])
Date: 2005-05-24 11:46:01
Vladimir Prus <ghost_at_[hidden]> writes:
> On Tuesday 24 May 2005 18:18, David Abrahams wrote:
>> building from libs/python/test
>>
>> For some reason <define>BOOST_PYTHON_SOURCE isn't getting applied,
>> even though it's in the target requirements for lib boost_python. Any
>> clues?
>
> Could it be that <define>BOOST_PYTHON_SOURCE is hiding inside rsp
> file?
It is not.
> You can check this with "bjam --v2 -n -a", I guess.
>
> Running "bjam -v2 -n msvc" (still on Linux), I get something like:
>
>
> echo "-DBOOST_PYTHON_SOURCE" >>
> "../../../bin.v2/libs/python/build/msvc/debug/wrapper_cpp.rsp"
>
> in the output.
Hum, it seems to be there now. I swear I checked it a few hours ago
and it wasn't.
The bigger problem is that .pyd files are coming out with the
extension .so instead:
msvc.link.dll ..\..\..\bin.v2\libs\python\test\polymorphism2.test\msvc-8.0\debug\polymorphism2_ext.so ..\..\..\bin.v2\libs\python\test\polymorphism2.test\msvc-8.0\debug\polymorphism2_ext-vc80-d-1_33.lib ..\..\..\bin.v2\libs\python\test\polymorphism2.test\msvc-8.0\debug\polymorphism2_ext.rsp
And then manifest generation fails.
-- Dave Abrahams Boost Consulting www.boost-consulting.com