Re: Digital Mars failures/toolset configuration question

From: Aleksey Gurtovoy (alexy_at_[hidden])
Date: 2005-06-17 12:15:45

David Abrahams writes:
> Aleksey Gurtovoy <alexy_at_[hidden]> writes:
>
>> David Abrahams writes:
>>> Dang. I'll try HTML-ifying and Cc you so you can't miss it:
>>>
>>> bjam &quot;-sBUILD=&lt;dmc&gt;&lt;*&gt;&lt;runtime-link&gt;&lt;static&quot;
>>
>> Doesn't have any effect. "-sBUILD=&lt;runtime-link&gt;&lt;static"
>> does, but naturally affects all the toolsets.
>
> Is your toolset really named "dmc"? 

Nope! It's "dmc-8_43-stlport-4_5_3".

> If not, you need the actual name of the toolset in the first angle
> brackets.

Oh, OK. I was assuming the above would match everything that starts
with "dmc".

>
>>> It was meant to be more like:
>>>
>>> {
>>> local v = BUILD ;
>>> if ! $(BUILD)
>>> {
>>> v = DEFAULT_BUILD ;
>>> }
>>> if ! &lt;dmc&gt;&lt;*&gt;&lt;runtime-link&gt;static in $($(v))
>>> {
>>> $(v) += &lt;dmc&gt;&lt;*&gt;&lt;runtime-link&gt;static
>>
>> Did you miss a semi-colon? 
>
> Yep.
>
>> If I add one, the bjam eats it but stops
>> building anything (just says "... found N targets..." and quits).
>
> O gawd, this is ridiculous. Well let me know if the toolset name is
> in fact "dmc" and we'll go from there.

FWIW, we just got the CD from Walter, which hopefully will allow us to
test with the current default link configuration, but I'd still like
to figure this out in particular because what we are trying to make to
work at the moment is the "default" Digital Mars distribution.

-- 
Aleksey Gurtovoy
MetaCommunications Engineering