I agree with Tamas that you are going to have hard-to-isolate problems mixing compiler versions. I have sort of a similar problem and I'm going to partially hijack this thread to see if anyone has any suggestions:
We use the latest version of GDAL we can (about to upgrade to 10.0.1) and try to use the latest compilers. Currently we build with gcc 4.4 and VS 2010 although we are eager to upgrade to gcc 4.6 and VS 2012. However, I don't think we can do so because we need MrSID support from GDAL and they (LizardTech) only support up to gcc 4.4 and VS 2010 with their DSDK and I want to avoid the mixed-compiler problems we're warning David about. Has anyone figured out a way to work around this limitation? Thanks very much, carl On Sat, Sep 7, 2013 at 3:21 AM, Tamas Szekeres <szeker...@gmail.com> wrote: > David, > > You should anyway use a consistent build along your system or make sure > you use your own version of gdal dll which is compatible with your plugin. > Mixing dependencies from different sources, compiled by different version > may cause unpredictable issues and crashes. You may either think to upgrade > your dll for VS2008 or isolate your application to load your specific > version. Not sure how that can be done technically without a more detailed > description of your software components/architecture. > > Best regards, > > Tamas > > > > > > 2013/9/6 David Szlucha <david.szlu...@exelisvis.com> > >> I have a GDAL plugin that is built with VS 2005 SP1 that I’m trying to >> use with a GDAL 1.8 DLL that was built with VS 2008. I cannot rebuild the >> GDAL 1.8 DLL as it is provided by a different vendor/application.**** >> >> ** ** >> >> I’ve found that the GDAL utilities crash when they are exiting (as well >> as some functionality in the vendor/application that our plugin was built >> for) in Windows 7. This does not seem to be a problem in Windows XP. **** >> >> ** ** >> >> I have limited information in the debugger but I suspect the issue might >> be in the GDAL driver manager deconstructor as I have created a “dummy” >> GDAL plugin that simply registers itself as a plugin and does nothing else >> and exhibits the same crash.**** >> >> ** ** >> >> After some internet searching it looks as if this problem has occurred >> with other GDAL plugins and the solution was to rebuild the plugin using >> the same compiler that built the GDAL DLL.**** >> >> ** ** >> >> Since my project consists of several other DLLs that I can’t readily be >> updated to VS 2008 I’m wondering if anyone has come across this issue in >> their own plugins and may have attempted to fix the issue with mixed >> compiler versions?**** >> >> ** ** >> >> Thanks!**** >> >> ** ** >> >> David**** >> >> _______________________________________________ >> gdal-dev mailing list >> gdal-dev@lists.osgeo.org >> http://lists.osgeo.org/mailman/listinfo/gdal-dev >> > > > _______________________________________________ > gdal-dev mailing list > gdal-dev@lists.osgeo.org > http://lists.osgeo.org/mailman/listinfo/gdal-dev >
_______________________________________________ gdal-dev mailing list gdal-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/gdal-dev
