> > > > Oh well probably doesn't matter too much. > > > > I think Microsoft wants people to use _fdopen() as fdopen() is depreciated. > > http://msdn.microsoft.com/en-us/library/dye30d82%28v=vs.80%29.aspx > > It seems quite crazy to not support standard function and provide a > replacement fully compatible, changing only its name. > > > I see now fdopen() is used in various places in Viking. > > > > May be one gets several warnings when compiling on Windows... > >
Now with my Windows build working, my patch to get the progress information from GPSBabel works. Since we use GCC (3.4.5) on Windows build, I'll keep it as fdopen() [since we use that elsewhere in Viking] as no compiler warnings are generated. I'll look to commit all my patches into the master and/or my github StagingPatches as appropriate over the next week; And create a Viking-1.3.2 branch/tag with a release for all systems, incorporating the Windows fixes and other key crash prevention patches such as the "Fix crashing when displayed map copyright(s) is longer than the internal buffer.", etc... Depending on how lucky I feel I may even try to address this too: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=685817 ------------------------------------------------------------------------------ Got visibility? Most devs has no idea what their production app looks like. Find out how fast your code is with AppDynamics Lite. http://ad.doubleclick.net/clk;262219671;13503038;y? http://info.appdynamics.com/FreeJavaPerformanceDownload.html _______________________________________________ Viking-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/viking-devel Viking home page: http://viking.sf.net/
