Hi, i have run into the exact same problem when the copy constructor of a multi_array is called. Is there a fix to get this working without the macros above? It is sadly no option to compile all dependencies from scratch. Regards -chris On Sun, Mar 14, 2010 at 3:29 AM, OvermindDL1 <overminddl1@gmail.com> wrote:
On Sat, Mar 13, 2010 at 10:34 AM, Jesse Perla <jesseperla@gmail.com> wrote:
Thomas Klimpel <Thomas.Klimpel <at> synopsys.com> writes:
#define _HAS_ITERATOR_DEBUGGING 0 ADD_DEFINITIONS(-D_HAS_ITERATOR_DEBUGGING=0)
Works like a charm. The only problem is that it looks like I have to compile every other library I use with the same definition or the linker gets angry. I may do that later.
Correct, and yes it does have a huge speed hit. In one specific project of mine, without putting that it runs in about 12 minutes, if I put that in then it runs in less then 100ms (or less then 10ms in release). Whoever was the retard that created those flags needs to have certain... er... catch my speech right quick...
Conseqently, for a few years now I use this in *everything* I compile, added to the end of every definition line in Visual Studio: ;_CRT_NONSTDC_NO_DEPRECATE;_CRT_SECURE_NO_DEPRECATE;_CRT_SECURE_NO_WARNINGS;_SECURE_SCL=0;_SCL_SECURE_NO_DEPRECATE;_HAS_ITERATOR_DEBUGGING=0
Or for CMake: /D_CRT_NONSTDC_NO_DEPRECATE /D_CRT_SECURE_NO_DEPRECATE /D_CRT_SECURE_NO_WARNINGS /D_SECURE_SCL=0 /D_SCL_SECURE_NO_DEPRECATE /D_HAS_ITERATOR_DEBUGGING=0
Or for BJam: -D_CRT_NONSTDC_NO_DEPRECATE -D_CRT_SECURE_NO_DEPRECATE -D_CRT_SECURE_NO_WARNINGS -D_SECURE_SCL=0 -D_SCL_SECURE_NO_DEPRECATE -D_HAS_ITERATOR_DEBUGGING=0
Etc... _______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost