Hi Robert. Like you, I'm frustrated by MS's new batch of errors and warnings. It's making my life difficult because I'm working on a few projects which started life in Vis Studio 6/7 or on Unix boxes without any of this hassle.
I suggested the change to the Vis Studio project settings because it fixes the non-compilation problem for those people effected by it, without breaking anything (that I'm aware of) for those it hasn't effected. > My work-around for this is to go into the project properties page, >Configuration Properties -> General and set >"Intermediate Directory" to $(temp)\$(ProjectName)\$(ConfigurationName) At the moment, if I download a new version of OSG, I have to compile on a local drive, then move the directory to my network account on a shared drive. Not really a problem, but it is one extra step, plus some time. I'm also with you on the second set of problems. However, the majority are down to the use of C style file operations and char strings, instead of C++ style iostream and std::string operations. For strcpy(), strcmp(), etc, MS say to consider #define _CRT_SECURE_NO_DEPRECATE 1 but when you read the help, they go on to say it doesn't work for dynamically allocated char arrays. You could turn the warnings off... #pragma warning( disable : 4996 ) but give me until the end of next week to see if I can clear them without the need to do this, because I don't really like to hide warnings. Gary. > ------------------------------ > > Message: 2 > Date: Wed, 9 Aug 2006 12:25:40 +0100 > From: "Robert Osfield" <[EMAIL PROTECTED]> > Subject: Re: [osg-users] Working towards OpenSceneGraph-1.1.1 release > To: "osg users" <[email protected]> > Message-ID: > <[EMAIL PROTECTED]> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > Hi Gary, > > On 8/9/06, Quinn, Gary <[EMAIL PROTECTED]> wrote: > > An issue with Visual Studio 7 and 8 is an error prevents > > anything compiling when you attempt to compile projects that > > are held on a windows share. > > I don't this is something we can fix within the OpenSceneGraph. > > > Also: As a result of compiling the CVS version of OpenScenegraph, > > with Visual Studio 8, I noticed a number of warnings. > > They don't prevent compilation, but I vaguely remember > > you saying that you like to have no errors and no warnings. > > See below for list. > > These warnings related to ANSC C usage that MS are deprecating in the > the name of security, but in the process making things alot more > awkward to make it cross platform. > > Franly I am unimpressed by this move and have little interest in > chasing up these warnings I am however very keen to fix real bugs, > and good warnings can help in this effort which is why I like to > compile things cleanly, however, bad warnings hide the good warnings > so you end up losts in this task. > > Is there a #pragma we can use to stop these warnings? > > Robert. > _______________________________________________ osg-users mailing list [email protected] http://openscenegraph.net/mailman/listinfo/osg-users http://www.openscenegraph.org/
