Hello Gerrit, "Johannes Brunen" <jbru...@datasolid.de> schrieb im Newsbeitrag news:ik3cdc$4tl$1...@dough.gmane.org... > > I think that I have found the problem. I did not correctly update > OSGConfig.h after checkout. The problem I have is that OpenSG does provide > the flag OSG_DISABLE_MICROSOFT_SECURE_CXXX which is OFF by default. If > defined, this flag handles the following set of defines > > _CRT_SECURE_NO_DEPRECATE > _CRT_SECURE_NO_WARNINGS > _CRT_NONSTDC_NO_DEPRECATE > _SECURE_SCL=0 > _SCL_SECURE_NO_WARNINGS > _SCL_SECURE_NO_DEPRECATE > _HAS_ITERATOR_DEBUGGING=0 > > Unfortunately, our code base has always defined > _HAS_ITERATOR_DEBUGGING=1 > and mixing to different policies is problematic. > > This combination is currently not supported by OpenSG and until now, I did > simply remove the corresponding section from OSGConfig.h on checkout. Not > quite correct, I did copy the OSGConfig.h from the last checkout which I > had already modified. So now, I introduced an inconsistency. Sorry for > that. > > After I have explained this all, may I ask for orthogonalization of the > first six flags and the last one? It should be simple by introducing a new > flag OSG_ENABLE_MICROSOFT_HAS_ITERATOR_DEBUGGING. Only OSGConfig.h and > UpdateCompiler.cmake would be affected. > sorry for beeing insistent. But I would really appreciate an additional cmake flag to handle the _HAS_ITERATOR_DEBUGGING switch. What do you think?
Best, Johannes ------------------------------------------------------------------------------ Enable your software for Intel(R) Active Management Technology to meet the growing manageability and security demands of your customers. Businesses are taking advantage of Intel(R) vPro (TM) technology - will your software be a part of the solution? Download the Intel(R) Manageability Checker today! http://p.sf.net/sfu/intel-dev2devmar _______________________________________________ Opensg-users mailing list Opensg-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensg-users
