Hi Chris,
I'll try to check, but since it's something I carefully avoid now, it may be a while.
Well as Roger said, it's generally something like "conflicting default libraries". But when someone who doesn't really know they shouldn't do that runs their project and it seems to work until it crashes while incrementing an iterator or something like that, they generally don't suspect that warning to be related to the problem. Plus some just ignore warnings altogether... As if the compiler was just being too fussy in telling you these things... :-)
To be clear, I agree the linker says "something", but I don't think it's near vocal enough to be useful to newbies / newcomers to Windows (on Linux you can mix debug and release however you want, no problem).
I liked the idea about intentionally messing with the code so that it wouldn't link if you messed it up, but it seems infeasible that you could prevent every combination of mismatch.
I agree, it would be nice. I don't see it as a problem that we can't catch every single type of mismatch... If we can at least catch some it's better than it is now. Just like the osgPlugins-<version> scheme was added to make it harder to mix plugins from different versions of OSG, but you can always put all the plugins in the same directory as the executable and then you're essentially defeating the scheme that's trying to protect you.
J-S -- ______________________________________________________ Jean-Sebastien Guay [email protected] http://www.cm-labs.com/ http://whitestar02.webhop.org/ _______________________________________________ osg-users mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
