Re: [gdal-dev] gdal-dev Digest, Vol 118, Issue 58

Hi， I have 2 suggestions： 1. supply an option that can build the gdal using the static c++ runtime library, so we can use it not depends on the msvcr80.dll and msvcp80.dll. 2. provide a gdal_merge.exe utility program with the same function as gdal_merge.py. here are the reasons I raise it:

Re: [gdal-dev] GDAL 1.11 release plan

Selon Olivier BARTHELEMY : I've fixed the one in adrgdataset.cpp. gifalloc.c, degrib18, hdf-eos are third-party code "imported" into GDAL tree. So the best way would be to fix the issues upstream (if fix is actually needed) and then downstream into GDAL. I've analyze errors reported in rasterlited

Re: [gdal-dev] GDAL 1.11 release plan

Here is what cppcheck 1.64 reports as 'errors' in gdal-1.10.1: [frmts\adrg\adrgdataset.cpp:1071]: (error) Memory leak: TILEINDEX [frmts\coasp\coasp_dataset.cpp:199]: (error) Undefined behavior: Variable 'pszItemValue' is used as parameter and destination in s[n]printf(). [frmts\dted\dted_create.c:

Re: [gdal-dev] GDAL 1.11 release plan

Hi Olivier, If you could share with us the errors that have been reported (and the options you have used to pass cppcheck on GDAL source), that would be a good contribution. Even better if you can submit a patch to fix them ;-) Not saying they shouldn't be fixed, but I don't see that as a blocker

Re: [gdal-dev] GDAL 1.11 release plan

I think you should take a look at what cppcheck finds when scanning GDAL source before the next release. There are a few tens of small errors. Mostly, small leaks in particalr cases. Not very important errors, but that ought to be fixed before doing an release in my opinion 2014-03-26 8:49 GMT+01

Re: [gdal-dev] GDAL 1.11 release plan

+1 for adding VS2013 binaries in GISInternals Thanks, Paul *Paul Meems * Release manager, configuration manager and forum moderator of MapWindow GIS. www.mapwindow.org Owner of MapWindow.nl - Support for Dutch speaking users. www.mapwindow.nl *Join us at the MapWindow GIS Conference 2014