Hello Sebastien,
But are you sure you are talking about an assert while deallocating memory of
an osg matrix list (my case) ??
What Robert is talking about is that when you link libraries and
executables that use a different runtime (for example, linking release
libraries into a debug executable), when any STL type is destroyed (for
example typedef std::vector< Matrix > osg::MatrixList ) the destructor
will crash because the structures have a different size in release than
in debug.
As Robert said, search the archives, it has been discussed a lot. In
essence, if you're building in release you need to make sure you're
linking to release OSG libs (and any other C++ lib) and if you're
building in debug you need to make sure you're linking to debug OSG
libs. That's the main reason why OSG binaries are available in both
release and debug. It's not optional, if you'll be building your app in
both release and debug you *need* both versions of OSG's libs and you
*need* to make sure your project's linker settings are set up correctly.
C-only libraries don't have this problem, so you can link a C-only
release lib to both debug and release executables, unless you intend to
go debug into the library's code.
Hope this helps,
J-S
--
______________________________________________________
Jean-Sebastien Guay jean-sebastien.g...@cm-labs.com
http://www.cm-labs.com/
http://whitestar02.webhop.org/
_______________________________________________
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
