Re: [Boost-build] static link enforcement ofr the toolset

From: Vladimir Prus (ghost_at_[hidden])
Date: 2007-10-19 01:30:09

Gennadiy Rozental wrote:

> 
> "Vladimir Prus" <ghost_at_[hidden]> wrote in message
> news:200710190908.26385.ghost_at_cs.msu.su...
>> On Friday 19 October 2007 02:03:56 Gennadiy Rozental wrote:
>>> How can I enforce Boost.Test users  for toolset msvc-6.5 to use
>>> exlusively
>>> static link?
>>>
>>> What should I put in users-requirements?
>>
>> You cannot do this.
> 
> Is this a technical limitation, or it's incorrect ideologically?

It's a complex behaviour which makes it hard to implement and hard 
to decide how actually it should work. Say you have a target that
uses both Boost.Test and libraryX. Boost.Test, when built,
returns <link>static requirements. But at this point, the
other dependent, libraryX, might already be built with <link>shared.

> Is there any alternative? Can add something in my test/Jamfile to enforce
> it for my own unit tests?

Yes, <toolset>msvc-6.5:<link>static

- Volodya