In order to avoid mixed CRT dependencies the developers should select the packages to match with their favourite compiler they are using actually. Another reason is to provide test environments for gdal and mapserver to make sure the projects can build equally well in the various compiler versions / architectures. At the time when gisinternals<http://www.gisinternals.com/sdk/>have been set up (in 2009) we didn't have any other alternatives to obtain x64 builds for these OSGeo projects, and this is also the case at the moment since osgeo4w-x64 is still experimental.
Tamas 2013/10/16 Thomas Heuberger <[email protected]> > just out of curiosity, why are there versions compiled with VC2k3 / 2k5 / > 2k8 / 2k10? Why not just say 2k10? > > > On Wed, Oct 16, 2013 at 4:02 PM, Tamas Szekeres <[email protected]>wrote: > >> It's already in my TODO list ( >> https://github.com/gisinternals/buildsystem/issues/9), but I still >> didn't have enough free time to work that out. >> >> Best regards, >> >> Tamas >> >> >> 2013/10/16 lightxx <[email protected]> >> >>> never mind. I still had that NuGet Post-build event hook in place which >>> replaced the dlls from the download with the NuGet ones that caused the >>> exception. Everything's working now, although I'd VERY MUCH prefer to use >>> the NuGet version. >>> >>> >>> >>> -- >>> View this message in context: >>> http://osgeo-org.1560.x6.nabble.com/Heap-corruption-when-using-GDALDriver-CreateCopy-C-Bindings-1-9-2-tp5083834p5083868.html >>> Sent from the GDAL - Dev mailing list archive at Nabble.com. >>> _______________________________________________ >>> gdal-dev mailing list >>> [email protected] >>> http://lists.osgeo.org/mailman/listinfo/gdal-dev >>> >> >> >
_______________________________________________ gdal-dev mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/gdal-dev
