Re: [jamboost] Re: [v2] ALL_LOCATE_TARGET capability?

From: Vladimir Prus (ghost_at_[hidden])
Date: 2004-12-15 03:00:02

On Tuesday 14 December 2004 20:09, David Abrahams wrote:

> >> >> 4. Allow primary and secondary project IDs, so people who want to
> >> >> can refer just to the secondary project ID (boost//)
> >> >
> >> > Hmm.. I'd rather not compicate projects ID further.
> >>
> >> I don't think this is really complicated. It's just a project alias. I
> >> think it's important if anyone wants to use versioned project IDs
> >> because they'll want to use the alias internally to that project anyway
> >> for maintenance reasons.
> >
> > There's a problem I see with computing build directory from project id
> > specified in "use-project". At the moment, build dir location is a
> > property of a project. So, when --build-dir is specified, we'd need to
> > get all "use-project" directives and modify build directories for the
> > affected projects. Workable, but not nice.
>
> I'm not sure I see that. Why do you think this feature has to change
> anything about build directory calculation?

You've lost me. The primary feature is --build-dir. We want it to work in 
presence of "use-project", so we want build directory of used project to be 
named according to the id in "use-project". So, we need to change build 
directory calculation somehow, no?

> > And what if you have
> >
> > use-project boost : /home/ghost/Work/boost ;
> > use-project boost-1.32 : /home/ghost/Work/boost ;
> >
> > Should this be an error? (Not that this is likely use case, but still we
> > need to consider this)
>
> Not an error. The first use-project assigns a primary project ID to
> that directory. The second one assigns a secondary project ID -- just
> an alias, like typedef in C++. The primary project ID is used for build
> directory calculation.

Looks ok to me.

- Volodya