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

From: David Abrahams (david.abrahams_at_[hidden])
Date: 2002-02-10 22:19:12

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

> Ahh, I'm there with you, what I did is even more flexible :-) I use a
global
> variable to map from the target type and the dependency type:
>
> gTARGET_TYPE_ID(pyd) = PYD ; # similar for others

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).

> >P.S. How does the idea of implementing the initialization and PWD
features
> >for V2 sit with you?
>
> I was expecting to :-] But I'm still working on the 2.4 Perforce merge.

How's it going? Need help? If you want to check in an intermediate state on
a branch, that might be a good idea.

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

-Dave