Re: [Boost-build] v2 Python toolset doesn't faithfully reproduce v1

From: Vladimir Prus (ghost_at_[hidden])
Date: 2006-07-22 08:09:43

On Saturday 22 July 2006 15:57, David Abrahams wrote:
> Vladimir Prus <ghost_at_[hidden]> writes:
> > Yep, we'll end up with two copies of symbols, but is this going to cause
> > real problems?
>
> Yes.

Are they already summarised somewhere? I've already changed not to do so, but 
it would be nicer to have rationale explained somewhere.

>
> > Anyway, I'll try to change this. That raises, again, this question: Do
> > we:
> >
> >    - Document that for embedding, application should be explicitly linked
> > to Python
>
> 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 not sure, I never tried to do this before. I think allowing this is a good 
idea, so I've added:

   https://zigzag.cs.msu.su:7813/boost.build/ticket/98

but we're not there yet.

> > 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?

I meant "/boost//python" -- the id of Boost.Python library.

- Volodya