wingrass, gdal, proj4
|Reported by:||hellik||Owned by:|
|Keywords:||wingrass, gdal, proj4||Cc:|
from the osgeo4w-ml:
I have updated the gdal-dev, libtiff, and libgeotiff packages from the respective trunks' and CVS heads. The gdal-dev package is now built with VC9 (Visual Studio 2008 Express). This greatest challenge with this proved to be mixups with alloc/free between the GDAL GeoTIFF driver's heap, and the libgeotiff heap since GDAL is built against the VC9 runtime/heap and libgeotiff is built against the VC7.1 runtime/heap. The fixes are back in GDAL trunk. This took *way* too much time for me to track down, isolate and fix but hopefully we are good till next time folks fiddle with the gt_wkt_srs.cpp code without realizing this issue. There seems to be no problem with building GDAL and it's python bindings with VC9 against the same Python we using VC7.1 with before. Somehow I thought there was an issue - but apparently not. I did have to take care to embed manifests. Once GDAL 1.8 is released I plan to build a gdal18 package using VC9 as a step towards reducing my dependence VC7.1 which is now antique, and not easily available to others. At that point I'm also hoping we can migrate most packages using GDAL to GDAL 1.8, to try and get out of the situation now where the default is ancient (1.5) and some packages (MapServer, QGIS) have moved to somewhat newer GDALs. This puts us in the ugly situation where people may end up having to install plugins for several versions of GDAL instead of install-once, use everywhere applying as I would like. I tried to package, and utilize the openjpeg jpeg2000 library but got caught up in some details and put it off. But this is likely our best hope for jpeg2000 read/write support that works well for large images without depending on proprietary libraries.
hi, I've read in the ML "gdal-dev, libtiff and libgeotiff upgraded" (http://lists.osgeo.org/pipermail/osgeo4w-dev/2010-October/001093.html) from time to time I'm building the "official" wingrass-installer. after updating according to "gdal-dev, libtiff and libgeotiff upgraded", I can find following updated files/folders in the osgeo4w-stack: C:\OSGeo4W\share\proj C:\OSGeo4W\share\epsg_csv C:\OSGeo4W\share\gdal AFAICT the actual wingrass-installers are built against osgeo4w-gdal-15. gdal and proj4 are dependencies for grass. which of the above mentioned (actualized) files/folders should be included in the wingrass-installers and for which above mentioned folders should be set GDAL_DATA and PROJ_LIB in order to get proj4 and gdal working properly? best regards Helmut (a little be confused and ...) p.s. "At that point I'm also hoping we can migrate most packages using GDAL to GDAL 1.8, to try and get out of the situation now where the default is ancient (1.5) and some packages (MapServer, QGIS) have moved to somewhat newer GDALs." ... very appreciated :o)
Helmut, They should all be include with wingrass. GDAL_DATA=C:\OSGeo4W\share\gdal PROJ_LIB=C:\OSGeo4W\share\proj GEOTIFF_CSV=C:\OSGeo4W\share\epsg_csv
AFAIK \share\gdal and \share\epsg_csv isn't included at the moment in the wingrass-installer: see GRASS-packager.bat
and GEOTIFF_CSV isn't set by the nsis-installer (http://trac.osgeo.org/grass/browser/grass/branches/releasebranch_6_4/mswindows/GRASS-Installer.nsi)
so wingrass-packaging and installing should be adapted acordingly?
best regards Helmut