Boost logo

Boost-Build :

From: David Abrahams (david.abrahams_at_[hidden])
Date: 2002-10-05 18:12:39

From: "Rene Rivera" <grafik666_at_[hidden]>

> I think there's an obvious way out... What I think you're after is a way
> changing the currently hardwired name of the library depending on the
> your doing. That's what having toolset and/or variant selectable
> requirements where designed for ;-) Here's the suggestion, add a define
> specifies the name of the target library file to the requirements of "dll
> boot_python", like so:
> <release><define>BOOST_PYTHON_NAME=\\\"\\\\"
> <debug><define>BOOST_PYTHON_NAME=\\\"\\\\"
> And then in your code use the BOOST_PYTHON_NAME instead of the literal
> string.
> The only problem with this is that then using the boos_python target from
> other places, like the test targets, will set the name incorrectly
> in those circumstances it needs the direct name ("").

Right. And that's no good either. The tests need to work, of course ;-)

David Abrahams * Boost Consulting
dave_at_[hidden] *


Boost-Build list run by bdawes at, david.abrahams at, gregod at, cpdaniel at, john at