Re: [Boost-testing] [repost][test][msvc-6.5_stlport4][speedsnail-msvc-dp] should we force static linking for Boost.Test on MSVC++ 6.5 + STLport?

From: Joaquin M Lopez Munoz (joaquin_at_[hidden])
Date: 2007-02-19 04:03:12

Joaquin M Lopez Munoz <joaquin <at> tid.es> writes:

> 
> Vladimir Prus <ghost <at> cs.msu.su> writes:
> 
[...]
 
> > Using a second requirement for stlport might be easier
> > and more direct solution.
> 
> You mean inserting an additional line like this?
> 
>   <toolset>msvc-6.5_stlport4:<link>static
> 
> The problem with that is that "msvc-6.5_stlport4" is AFAIK
> just a convenient name chosen by Roland, so relying on it
> feels like a hack. Doesn't BBv2 provide any other means
> to check whether STLport is being used other than
> guessing from the toolset name?
> 

Hello, allow me to reclaim your attention to this. Would
the following do in order to extend the static forcing
to "msvc-6.5_stlport4"?

lib boost_unit_test_framework : $(UTF_SOURCES).cpp
        : <toolset>msvc-6.5:<link>static
          <toolset>msvc-6.5_stlport4:<link>static
        ;

Roland, Vladimir? I can't test this myself, and there are
several red cells still pending to be cleared. As I
said in my previous post, I would prefer a more elaborate
requirement dealing directly with the stdlib being used
rather than relying on the toolset name, but as I got
no response please at least check this simpler hack.
Thank you very much,

Joaquín M López Muñoz
Telefónica, Investigación y Desarrollo