From: David Abrahams (dave_at_[hidden])
Date: 2006-07-22 07:57:39
Vladimir Prus <ghost_at_[hidden]> writes:
> Yep, we'll end up with two copies of symbols, but is this going to cause real
> Anyway, I'll try to change this. That raises, again, this question: Do we:
> - Document that for embedding, application should be explicitly linked to
Not bad, but not necessary.
> - Add new target "boost_python_for_embedded", that will alias to
> Boost.Python, Python, and any auxilliary libraries.
Also not bad.
Is it impossible to make conditional usage requirements where the
condition is "what type of target are we building?"
> I'm fine with just adding /boost/python to all embedding applications, as far
> as tests are concerned.
What is /boost/python (a path?) and how does it get added?
> You know better, though.
Not sure I do.
-- Dave Abrahams Boost Consulting www.boost-consulting.com
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