Hi Tom -- My guess is your VS 2003 app is not compatible with VS 2005 c runtime libs. If you were to also copy the VS 2003 c runtime libs to the other machine, or use something like InstallShield to pick them up and package them and install them, then that should work.
As J-S said, this problem is not limited to OSG but is a general issue with any VS app. Paul Martz Skew Matrix Software LLC http://www.skew-matrix.com +1 303 859 9466 -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Appolloni, Thomas Sent: Friday, May 01, 2009 12:30 PM To: [email protected] Subject: [osg-users] Changing Versions of Visual Studio I have been working exclusively with Visual Studio 2003 and now I'm dealing with different machines with newer VS versions on them. My question is: With each version of Visual Studio, does there need to be a separate OSG build? The first problem I saw was something as simple as the code snippet below: 1 osg::ref_ptr< osg::Group > theRoot = new osg::Group; 2 theRoot->setName("Root"); 3 cout << theRoot->getName(); This executes just fine on my current machine with VS2003 (under which OSG was compiled ). However when I copy that baseline over (with the same OSG lib/dll files) to a machine with VS2005 on it, compile it and run that same code, it crashes on line 3. I didn't think it should need a rebuild but I don't see what else might cause that problem. I thought I'd ask if indeed OSG needs to be rebuilt for each VS version while I'm looking for other causes. Thanks, Tom _______________________________________________ osg-users mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org _______________________________________________ osg-users mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
