[gdal-dev] Gdalinfo does not print into file on Windows

[Even Rouault]

Selon Andre Joost <andre+joost at nurfuerspam.de>:

> Am 17.09.2013 17:02, schrieb Even Rouault:
> > Hi Jukka,
> >
> > This reminds me a lot the following ticket :
> > http://trac.osgeo.org/gdal/ticket/5128
> >
> > Could you confirm that the analysis done (i.e. the cause of the problem
> would be
> > the ECW plugin) also applies to you ? I'm not sure if you must completely
> > uninstall (or rename) the gdal_ECW.dll, or if specifying GDAL_SKIP=ECW as
> > environmenet variable is sufficient
>
> Confirmed here. Removing or renaming the gdal_ECW_JP2ECW.dll in \bin
> solves the problem. The file investigated was a .tif, so the ecw driver
> was not used at all. Tested on gisinternals sdk version 1-10-0 from
> 07.09.2013.

Hum, this is an interesting (=annoying) issue. Here's the result of my tests
(only on 32 bit builds) :
- release-1600-gdal-1-10-mapserver-6-2 : bad
- release-1600-gdal-1-9-1-mapserver-6-0-3 : bad
- release-1400-gdal-mapserver (latest dev version): bad
- release-1500-gdal-mapserver (latest dev version): bad
- release-1400-gdal-1-8-1-mapserver-6-0-1 : bad
- release-1310-gdal-mapserver (latest dev version): ... good ...
- release-1310-gdal-1-8-1-mapserver-6-0-1 : good

So my conclusion is that it does not depend on the GDAL version, but it does
depend on the MSVC compiler. And apparently only MSVC 1310 pleases the ECW SDK.
The issue must be a bad interaction between the old ECW SDK 3.3 code and MSVC >=
1400.

I've reported it as https://github.com/gisinternals/buildsystem/issues/36 to
Tamas as this is more a packaging issue, but I'm not sure what can be done in
practice. Unless someone is willing to debug that. Perhaps the issue has gone
with newer versions of the ECW SDK.

>
> HTH,
> André Joost
>
> _______________________________________________
> gdal-dev mailing list
> gdal-dev at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/gdal-dev
>