From: Vladimir Prus (ghost_at_[hidden])
Date: 2005-05-27 10:29:34
On Tuesday 24 May 2005 21:04, David Abrahams wrote:
> David Abrahams <dave_at_[hidden]> writes:
> > 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.
> Well, here we go again. in libs/python/test I built again, and the
> .rsp in question contains only:
> and in fact here are all the commands that get generated for that
Ah, so this happens when compiling tests. Wait a minute, when compiling
*tests*, you don't need BOOST_PYTHON_SOURCE, right? So, eventhing looks
correct. Am I missing something?
-- Vladimir Prus http://vladimir_prus.blogspot.com Boost.Build V2: http://boost.org/boost-build2
Boost-Build list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk