Hi all -- I only caught bits and pieces of the discussion regarding changing
the way that warnings are handled in Visual Studio. I know they used to be
eliminated with #pragmas in the source code, and I assume they are now
eliminated with the /W option (when USE_AGGRESSIVE_WARNINGS is OFF).
 
I have about 30 or so projects that include OSG headers, and nearly all of
them are generating several hundred warnings when compiled with VS against
current OSG svn. They all compiled cleanly before this change.
 
When you folks were discussing this change, what decision did you make about
external projects? Were you thinking that all external projects should
stifle the warnings by using /W?
 
If anyone knows of a way to do this without manually modifying all of my ~30
projects, I would really appreciate it. I'm not looking forward to doing
this manually.
 
Paul Martz
Skew Matrix Software LLC
http://www.skew-matrix.com <http://www.skew-matrix.com/> 
+1 303 859 9466
 
_______________________________________________
osg-users mailing list
[email protected]
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

Reply via email to