Re: [Boost-build] Many lingering v1 dependencies

From: Vladimir Prus (ghost_at_[hidden])
Date: 2007-01-12 15:22:14

On Friday 12 January 2007 06:18, David Abrahams wrote:
> Vladimir Prus <ghost_at_[hidden]> writes:
> 
> > On Saturday 06 January 2007 17:58, David Abrahams wrote:
> >> Vladimir Prus <ghost_at_[hidden]> writes:
> >> 
> >> > On Sunday 10 December 2006 17:33, David Abrahams wrote:
> >> >> 
> >> >> I keep seeing BBv1 dependencies in our supposedly-v2 scripts,
> >> >> Jamfiles, and documentation.  For example $BOOST_ROOT/Jamfile.v2 uses
> >> >> the --with-python-root option to set the PYTHON_ROOT variable, which
> >> >> has no effect in v2.  
> >> >
> >> > This specific issue is:
> >> >
> >> > 	https://zigzag.cs.msu.su:7813/boost.build/ticket/61
> >> >
> >> > I'm don't know what's right solution to it, do you?
> >> 
> >> Get the person who wrote the Jamfile to remove the v1 idioms?
> >
> > That's rather imprecise. If you want *me* to fix that, you'd need to
> > tell me exactly that the --with-python-root should do. 
> > Especially when python is already initalized in user-config.jam.
> 
> You can either remove it because we can't support it, or get it to do
> the right thing, somehow.  Leaving the option in, but functioning
> incorrectly, and documented in the --help usage output is simply
> *unacceptable*.
> 
> It's not my job to tell you how you should get it to do the right
> thing, but I am willing to discuss the possibilities with you if you
> think supporting --with-python-root is important.

I don't even know what it does, how can I decide if we need to keep it.
You know what Boost.Python users want, so can you say if you:

        - want me to implement that option, and specify how
        it should work.
        - want me to remove it
        - want something else.

> >> >> http://www.boost-consulting.com/boost/more/separate_compilation.html
> >> >> still needs to be updated for BBv2.  
> >> >
> >> > Is there a ticket for it?
> >> 
> >> I don't know.  Is it a BB issue?
> 
> ??

It can be considered such. Anyway, I think it's fixed now.

- Volodya