Vladimir Prus wrote:
Ben Pope wrote:
> And for completeness and the sake of comparison (and for when we move
> to 1.34) what is the equivalent with BBv2? I've noticed that there is
> some conditional stuff:
> <variant>release:<define>_SECURE_SCL=0
> But couldn't work out how to do it on the command line, do I need to
> create some jam config files?
In 1.34, you'd have to:
1. Add
<toolset>msvc:<define>_SECURE_SCL_0
to 'requirements' section in boost_root/Jamfile
Hello,
I have the same problem, with boost 1.34, but could not understand your answer: I did not find what you call the 'requirements' section in boost_root/Jamfile. The closest I could find is:
project boost
: requirements <include>.
# disable auto-linking for all targets here,
# primarily because it caused troubles with V2
<define>BOOST_ALL_NO_LIB=1
# Used to encode variant in target name. See the
# 'tag' rule below.
<tag>@$(__name__).tag
<conditional>@handle-static-runtime
: usage-requirements <include>.
: build-dir bin.v2
: default-build $(default-build)
;
Should I add it there ? Morever, in the line you specify, I cannot see where you specify that the flag should not be used for debug builds.
Finally, I'm a little bit nervous in modifying those kind of files... Couldn't such an option be set by modifying user-config.jam ? The best I could find was adding the following line in this file:
using msvc : : : <compileflags>-D_SECURE_SCL=0 ;
But I could not find a way to set a different value depending on the variant. Currently, I modify this file before recompiling.
Best regards,
--
Loïc
