Boost C++ Libraries: Ticket #2086: Add build option to define _secure_scl=0 + add runtime check to ensure no ODR violation https://svn.boost.org/trac10/ticket/2086 <p> The binary incompatibily caused by this macro is a bit of a headache, and figuring out how to set it from bjam is not well documented. </p> <p> It does mean one has to recompiling boost a few times to get it right. </p> <p> I'd be delighted for having a bjam setting for this (with an additional -xx- on the lib/dlls). </p> <p> Extra bonus for a check somewhere that compares the user's setting with that of the compiled dll. (f.ex. by a generating a .hpp-file during build that everyone includes and does #if(n)def _SECURE_SCL / #error (inconsistent build options) ) </p> en-us Boost C++ Libraries /htdocs/site/boost.png https://svn.boost.org/trac10/ticket/2086 Trac 1.4.3 anonymous Wed, 23 Jul 2008 07:06:25 GMT <link>https://svn.boost.org/trac10/ticket/2086#comment:1 </link> <guid isPermaLink="false">https://svn.boost.org/trac10/ticket/2086#comment:1</guid> <description> <p> Nearly any #definition may introduce ODR violation. It is impossible to provide a separate boost build feature for every such a #definition. </p> <p> The correct syntax is quite simple: $ bjam define=your_definition </p> </description> <category>Ticket</category> </item> <item> <dc:creator>Vladimir Prus</dc:creator> <pubDate>Sat, 21 Mar 2009 23:01:46 GMT</pubDate> <title>status changed; resolution set https://svn.boost.org/trac10/ticket/2086#comment:2 https://svn.boost.org/trac10/ticket/2086#comment:2 <ul> <li><strong>status</strong> <span class="trac-field-old">new</span> → <span class="trac-field-new">closed</span> </li> <li><strong>resolution</strong> → <span class="trac-field-new">invalid</span> </li> </ul> <p> Closing this issue based on explanation in the comment. </p> Ticket