Re: [boost] [RFC] Boost library name mangling and Microsoft's 'secure STL' feature.

Subject: Re: [boost] [RFC] Boost library name mangling and Microsoft's 'secure STL' feature.
From: Marcus Lindblom (macke_at_[hidden])
Date: 2008-09-04 04:36:41

dherring_at_[hidden] wrote:
> On Wed, 3 Sep 2008, Jurko Gospodneti? wrote:
>>     * If the setting is 'on' the name would get en extra letter 'c'
>> added to its 'runtime tag' letter group (together with 's' for
>> statically linked libraries, 'd' for debug, 'p' for the stlport standard
>> library, etc.).
> 
> Does the MSVC library ABI change depending on whether "secure STL" has 
> been enabled?  If not, I'd suggest adding a build option but not adding 
> yet another runtime tag.

It does, so it is impossible to link incompatible binaries. :(

We had to adjust site-config.jam and recompile boost to get it to work, 
since we disable these iterators by default. (Their performance hit is 
too severe.)

Cheers,
/Marcus