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

From: Rene Rivera (grafik666_at_[hidden])
Date: 2002-02-10 20:42:26

On 2002-02-10 at 07:15 PM, david.abrahams_at_[hidden] (David Abrahams) wrote:

>> * Also, because of the names, Python use needed to change. Because the PYD
>> type is a real target type, even if it's mostly a DLL, one needs a
>different
>> type specifier when depending on those targets. For now I use "<pyd>" but
>if
>> you have a better name that would be great.
>
>pyd is fine. Maybe the thing to do is to look for grist, extract the part
>between <> and upcase the name to get the target type. That would make it
>completely general.

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

>> Again, I don't know how many people this is going to affect, but it's
>going to
>> require changes to any Jamfiles that create or depend on DLLs. I have
>changes
>> for regex, threads, and python, which covers all the "external" ones in
>Boost.
>>
>> So Dave, unless you some problems with the above I'll go ahead commit the
>> changes.
>
>No problems, but you should alert John Maddock and Bill Kempf since these
>are their projects.

Will do!

>-Dave
>
>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. And I
have to think more about the difficulties that Vladimir brought with the crawl
up behaviour.

-- grafik - Don't Assume Anything
-- rrivera_at_[hidden] - grafik_at_[hidden]
-- 102708583_at_icq - Grafik666_at_AIM - Grafik_at_[hidden]