Re: [jamboost] STLPort without iostreams gets wrongly named in bjam v1

From: Rene Rivera (grafik.list_at_[hidden])
Date: 2004-08-02 09:39:09

John Maddock wrote:

> When I execute:
> 
> bjam -n -sTOOLS=vc7.1-stlport -sBUILD="<stlport-iostream>off
> <runtime-link>dynamic"
> 
> The libraries don't get an "n" suffix mangled into them as they should
> according to the docs (the auto-link code follows the docs), any ideas?

OK, looked into it... This is a combination of two bits of code:

1. In the vc7.1-stlport-tools.jam there is this:

# STLPort doesn't support <stlport-iostream>off with vc7.
# This is essentially a usage-requirement on the stlport library.
local gBUILD_PROPERTIES = [ difference $(gBUILD_PROPERTIES) : 
<stlport-iostream>off ] <stlport-iostream>on ;

That makes it so that regardless of what your set as the BUILD 
stlport-iostreams are always on for vc71. Even if the variant has the 
../stlport-iostreams-off/.. subdir. And..

2. In boost-base.jam there is this:

# <stlport-iostream> is always on, no matter what we may think
# this is an stlport build requirement.
runtime-tag = [ difference $(runtime-tag) : n ] ;

Which removes the "n" from the tag to compensate for #1 above.

So in a way it's doing the correct things. But it's also misleading.

-- 
-- Grafik - Don't Assume Anything
-- Redshift Software, Inc. - http://redshift-software.com
-- rrivera/acm.org - grafik/redshift-software.com - 102708583/icq