|
Boost : |
Subject: Re: [boost] _SECURE_SCL for msvc
From: Thorsten Ottosen (nesotto_at_[hidden])
Date: 2009-02-12 05:07:08
Hansi skrev:
> Hello,
>
> the problem with _SECURE_SCL define was already discussed a few times on
> this list. But til now it came never to a end.
> Is there any interrest to get also compiled libraries for _SECURE_SCL
> enabled and _SECURE_SCL disabled?
Yes. I define
import feature ;
#
# Composite feaure that ensures <define> can propagate
# to all dependencies, not just sub-projects.
#
feature.feature secure-stl : on off : propagated composite optional ;
feature.compose <secure-stl>off : <define>_SECURE_SCL=0
<define>_CRT_SECURE_NO_DEPRECATE=1
<define>_SCL_SECURE_NO_DEPRECATE=1
<define>_CRT_NONSTDC_NO_DEPRECATE=1 ;
And then add
<secure-stl>off
to the requirements.
I am in favor of libraries being named differently, eg. with "_nsc" suffix.
-Thorsten
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk