[GRASS-dev] Re: [GRASS GIS] #885: WinGrass: displaying r.external-linked raster data not working

GRASS GIS trac at osgeo.org
Wed Jan 20 00:05:17 EST 2010


#885: WinGrass: displaying r.external-linked raster data not working
------------------------------+---------------------------------------------
  Reporter:  hellik           |       Owner:  grass-dev at lists.osgeo.org
      Type:  defect           |      Status:  new                      
  Priority:  critical         |   Milestone:  6.4.0                    
 Component:  Display          |     Version:  svn-releasebranch64      
Resolution:                   |    Keywords:  r.external, WinGrass     
  Platform:  MSWindows Vista  |         Cpu:  x86-32                   
------------------------------+---------------------------------------------
Comment (by glynn):

 Replying to [ticket:885 hellik]:
 > fresh Grass64svn, self compiled,
 > nc-sample-dataset
 >
 > elevation exported as gtiff
 >
 > linking by r.external seems to work

 > basic information raster of the linked data is available

 > but if i want to display the linked raster in the wxgui, following error
 message comes up:
 >
 {{{
 "Error: Unable to locate symbol <GDALAllRegister>
 }}}

 I suspect that it needs to be e.g. `GDALAllRegister at 0`, as the functions
 use the "stdcall" (aka "pascal") calling convention.

 It works with the version of GDAL I have here (which I built from source),
 which for some reason seems to be using "ccall" (the symbols don't have
 the @<size> suffix).

 You could try using "`make GDAL_DYNAMIC=`" to link libgis directly against
 GDAL, rather than using `LoadLibrary()`.

 To make it work with a stdcall version of GDAL, I need to know the
 decorated names.

 OTOH, it may be better to simply omit the r.external support from 6.5;
 it's very out of date (it was back-ported shortly after the first draft of
 the code was added to 7.0, and hasn't been updated since).

-- 
Ticket URL: <http://trac.osgeo.org/grass/ticket/885#comment:1>
GRASS GIS <http://grass.osgeo.org>


More information about the grass-dev mailing list