On 5 May 2016 at 01:45, Even Rouault <even.roua...@spatialys.com> wrote: > Of the potential issues with requiring C++11, I can think of OSGeo4W. It is > mostly(completely?) built with Visual Studio 2010. And from > https://msdn.microsoft.com/en-us/library/hh567368.aspx , support of C++11 is > only partial in VS 2010
VS2013 is the lowest version sensible to consider regarding C++11 support. > On the other hand regarding dependencies of GDAL, the binary propritary SDKs > with a C++ API could be a problem, although they will likely move on too. > - FileGDB SDK 1.4: available for VS2010, VS2012, VS2013 > - ECW SDK 5.2.1: available for VS2010, VS2012, VS2013 AFAICT, GDAL built using VS2015 links against the 5.2.1 version fine. > - MrSID SDK: I didn't check. Perhaps Kirk can tell us ? Similarly to the ECW above, version 9.1.0 links fine too. > But I'm not sure about the compatibility of C++11 build against non-C++11 > builds in the VS realm : can a GDAL C++11 build link against a library built > without C++11 enabled ? Will not there be ABI problems ? Although mixing C run-time libraries is a bad idea generally, kosher C APIs should be fine. Best regards, -- Mateusz Loskot, http://mateusz.loskot.net _______________________________________________ gdal-dev mailing list gdal-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/gdal-dev