[postgis-devel] [PostGIS] #1158: Can't compile under Windows mingw

PostGIS trac at osgeo.org
Wed Aug 17 19:48:14 PDT 2011


#1158: Can't compile under Windows mingw
---------------------+------------------------------------------------------
 Reporter:  robe     |       Owner:  strk         
     Type:  defect   |      Status:  new          
 Priority:  blocker  |   Milestone:  PostGIS 2.0.0
Component:  postgis  |     Version:  trunk        
 Keywords:           |  
---------------------+------------------------------------------------------

Comment(by bnordgren):

 Something is mighty hoakey. I started having similar problems when
 preparing the patch for #1161. As it turns out, whenever I moved a
 function to libpgcommon which needed to be exposed to sql, I started to
 have problems with the regression. I settled on moving only the C
 functions, and not things like:

 {{{
 PG_FUNCTION_INFO_V1(transform_geom);
 Datum transform_geom(PG_FUNCTION_ARGS)
 {
 ...
 }
 }}}

 The hoakey part is that `transform_geom` has been moved to libpgcommon in
 my build too, and the regressions pass just fine. Same platform, same
 concept (moving a V1 PG_FUNCTION to libpgcommon from postgis), two
 different results. This seems to be a very strange linker issue. Perhaps
 it would be wiser to keep all the V1 PG functions in `/postgis` or
 `/raster`, and factor out only the C code.

 Besides, we really don't want to expose `transform_geom` to SQL from both
 the postgis and raster modules, I don't think...

-- 
Ticket URL: <http://trac.osgeo.org/postgis/ticket/1158#comment:30>
PostGIS <http://trac.osgeo.org/postgis/>
The PostGIS Trac is used for bug, enhancement & task tracking, a user and developer wiki, and a view into the subversion code repository of PostGIS project.


More information about the postgis-devel mailing list