Quoting Andy Ross : > Vance Souders wrote: > > Microsoft has made major changes to the standard C++ and C > > runtime libraries under Visual Studio 2005. When compiling > > Flightgear 0.9.9 under VS 2005, you get about 2500 deprecated > > function warnings because of these changes. So, to build FG > > under VS 05 with zero errors and zero warnings is going to take a > > lot of minor code changes. > > It would be more helpful if you would post the warnings. Surely > MS hasn't broken any pre-existing compatibility with the ANSI C++ > library, so most of the warnings are most likely ambiguities that > can be fixed without trouble. > > Note that if you set yourself up to compile on cygwin/gcc also, > you'll be able to see almost the same warning environment that > the Linux folks have, also.
It says that strcpy ( for instance ) is not secure and one should use strcpy_s that is the secured version. Maybe I missed something, but I don't thing strcpy_s is available outside the MS world. As these warning are issued on the C run time library, one move could be to use the C++ STL instead ( the std::string class in that case ). -Fred ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid3432&bid#0486&dat1642 _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
