Add build option to define _secure_scl=0 + add runtime check to ensure no ODR violation

[Marcus Lindblom <macke@…>]

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.

It does mean one has to recompiling boost a few times to get it right.

I'd be delighted for having a bjam setting for this (with an additional -xx- on the lib/dlls).

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

[anonymous]

Nearly any #definition may introduce ODR violation. It is impossible to provide a separate boost build feature for every such a #definition.

The correct syntax is quite simple: $ bjam define=your_definition

[Vladimir Prus]

Closing this issue based on explanation in the comment.