Re: [jamboost] Boost.Build, legacy changes...

From: David Abrahams (david.abrahams_at_[hidden])
Date: 2002-02-10 23:58:48

----- Original Message -----
From: "Rene Rivera" <grafik666_at_[hidden]>

> >A bit more work for new target types, but no worries, this branch of the
> >code is dead anyway ;^). In future we'll specify these things with rule
> >invocations (and some sort of variables only under-the-covers).
>
> I would hope that we don't use variables at all in the new system :-) It
would
> make more sense to make the target types objects.

All state, including the state of objects, is eventually stored in
variables.

> But that supposses that we use the object system on V2.

It's already in use in feature.jam/build-request.jam.

> >> And I
> >> have to think more about the difficulties that Vladimir brought with
the
> >crawl
> >> up behaviour.
> >
> >I wasn't really clear on what the problem was. Wasn't he just contending
> >that crawl-up should use GLOB to look for the files? I was expecting that
> >anyway.
>
> Nah, that's the easy part :-) The hard question is what happens when we
> include a Jamfile from an "external" project. Do we search for the
> project-root.jam again?

Yes, if only to get rules and configuration associated with that project.
What's the problem?

> And if so we have to do the search relative to the Jamfile we are
including.

Right.

> And I'm sure there are other problems I can't think
> of right now that "external" inclusion brings up.

I guess I still don't see anything mysterious here.

-Dave