From: John Maddock (john_at_[hidden])
Date: 2004-03-22 07:20:27
> I discovered to my dismay that the boost_thread lib that uses STLport uses
> STLport's special debug mode. I therefore prepared a patch (against
> that renames the current 'debug' target to 'stldebug' and adds a new
> target that only uses the normal debug version of STLport.
> There are a few issues to discuss though:
> - I'm no expert of the build-system, not even an adept. I just tried to
> understand what's going on and tried until it seemed to work. It is a
> tested on MSVC6.
> - I have no idea why the special debug-mode was introduced as default in
> first place, I haven't found anything that tells why.
> - I found a note in one of the bbuild v2 files (which I did neither use
> patch) saying that 'normal debug' is not supported. Again, why and why
> that stated in the notes for the *-stlport toolsets?
> - regex(IIRC) uses a 'd' in the resulting lib to mark debug libs and 'dd'
> mark libs with special debug modes like STLport's. I adapted this naming
> convention when making the patch.
regex now uses the same convensions as Boost.Build, there is no longer a
debug build that doesn't use the STLPort debug mode.
> In case anyone wonders, I work in an environment where I just don't have
> extra time for STLport's debug mode.
No extra time required, just define __STL_DEBUG, it's defined by default for
Boost+STLPort because it catches coding errors that otherwise can slip
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk