From: Rene Rivera (grafikrobot_at_[hidden])
Date: 2006-11-19 18:50:37
Note... My response below is from what I remember. I'd have to examine
the BBv1 STLport support carefully to answer this precisely. But since
the BBv2 STLport is different, and since STLport no longer has a native
IO mode it may not matter :-)
David Abrahams wrote:
> I believe http://boost.org/more/getting_started.html may be conflating
> the compiler's runtime support library with the standard library
> (which admittedly are sometimes the same). Consider the case
> mentioned there:
> For example if you compile debug code for STLport using native IO
> streams, and statically link to the debug runtime the tag would be:
> STLPort's native IOstreams feature means there's no compiled STLPort
> I presume that when not using native iostreams, 'g' selects the
> debug version of the STLPort binary.
> When using native iostreams,
> * Does it enable STLPort debug mode?
> * Does it use a debug version of the compiler's runtime library?
Basically when the user requests a debug runtime, it both tells the
compilers to use debug mode and when using STLport it uses the debug
-- -- Grafik - Don't Assume Anything -- Redshift Software, Inc. - http://redshift-software.com -- rrivera/acm.org - grafik/redshift-software.com -- 102708583/icq - grafikrobot/aim - grafikrobot/yahoo
Boost-Build list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk