Re: [jamboost] [Q] stlport in V2 -- How to configure?

From: Vladimir Prus (ghost_at_[hidden])
Date: 2004-11-18 02:28:21

On Thursday 18 November 2004 02:15, Michael Peterson wrote:
> Anyone,
>
> I've just installed STLport-5.0-0125 and boost_1_31_0. I want to use
> bbv2 and so I've setup my environment so that bjam --v2 is invoked.
>
> However, I've learned via the bbv2 docs that the old command line,
>
> bjam "-sTOOLS=gcc-stlport" ...
>
> no longer works and than I need to use this
>
> bjam toolset=<name of toolset> ...
>
>
> What is the toolset name I need to use that is equivalent to
> 'gcc-stlport'? 

There's none, you'd use <toolset>gcc, because in V2 toolsets are orthogonal 
from stlport.

> Also, how do I control whether to use stlport's i/o 
> streams, etc. ala bbv1?

Here's the comment from v2/tools/stlport.jam:

# The STLPort is usable by means of 'stdlib' feature. When
# stdlib=stlport is specified, default version of STLPort will be used,
# while stdlib=stlport-4.5 will use specific version.
# The subfeature value 'hostios' means to use host compiler's iostreams.

So,

bjam toolset=gcc stdlib=stlport 

would use stlport, and 

bjam toolset=gc stdlib=stlport-hostios

would use stlport with gcc iostreams.

As usual, appropriate

using stlport : .......... ;

is needed. The parameters can be obtained with

bjam --help stlport.init 

I have: 

using stlport : : /usr/include/stlport ;

and can successfully run

bjam stdlib=stlport runtime-debugging=off

in example/hello. (I don't have debug version of STLPort installed, that's why 
runtime-debugging is off above).

- Volodya