$include_dir="/home/hyper-archives/boost-build/include"; include("$include_dir/msg-header.inc") ?>
From: Vladimir Prus (ghost_at_[hidden])
Date: 2006-04-26 03:00:42
On Friday 21 April 2006 18:15, David Abrahams wrote:
> Zbynek Winkler <zw-bjam_at_[hidden]> writes:
> >>If you don't have time to design it all, but have some ideas, please
> >> speak out. Note, especially, that you don't need to have any deep
> >> knowledge of V2 *code*, you just need to think about the best user
> >> interface, so it's a good way to affect V2 without learning jam language
> >> ;-)
> >>
> > :-)
> >
> > For (1) I think the generator should be given a chance to decide which
> > properties make sense for the target being built. Thus generating pdf
> > from tex wouldn't have to end up in debug directory but a C compiler
> > would respect it.
>
> In BBv1 we had the concept of "relevant" properties. Properties that
> weren't relevant to the toolset would never show up in the target
> path. We should be doing the same thing with generators in BBv2. If
> we're not, why not?
Because it's not implemented, and scheduled for M12:
https://zigzag.cs.msu.su/boost.build/ticket/4
I'm just wondering what other approaches for shortening targets paths are
available.
- Volodya
-- Vladimir Prus http://vladimir_prus.blogspot.com Boost.Build V2: http://boost.org/boost-build2