« Return to Thread: Building Boost 1.33.1 with different #defines for release and debug

Re: Building Boost 1.33.1 with different #defines for release and debug

by Vladimir Prus :: Rate this Message:

Reply to Author | View in Thread

Loïc Joly wrote:

>
>
>
> 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>.

Yes, it's it.

> 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.

Err, I have no idea what what define is, and if it should be on for
release builds, or not. Something like:

        <toolset>msvc,<variant>release:<define>_SECURE_SCL_0

should catch just release 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 ?

Yes, add said thing to project requirements on user-config.jam.

- Volodya


_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build

 « Return to Thread: Building Boost 1.33.1 with different #defines for release and debug