[osgeo4w-dev] [osgeo4w] #305: python/sqlite: "sqlite3-rtree-geometry-callback" not found in "C:\OSGeo4W\apps\Python27\DLLs\sqlite3.dll"

[OSGeo4W]

#305: python/sqlite: "sqlite3-rtree-geometry-callback" not found in
"C:\OSGeo4W\apps\Python27\DLLs\sqlite3.dll"
---------------------+------------------------------------------------------
Reporter:  hellik    |       Owner:  brushtyler   
    Type:  defect    |      Status:  new          
Priority:  critical  |   Component:  Package      
 Version:  1.0       |    Keywords:  python,sqlite
---------------------+------------------------------------------------------

Comment(by hellik):

 Replying to [comment:23 brushtyler]:
 > Replying to [comment:21 hellik]:
 > > Replying to [comment:19 brushtyler]:
 > > > in SpatiaLite 3.0.1 (the version shipped with OSGeo4W) the name of
 the flag is '''OMIT_GEOCALLBACKS''', probably it was changed to
 DISABLE_GEOMETRY_CALLBACKS in the last splite version.
 > >
 > > {{{
 > >   --enable-geocallbacks   enables geometry callbacks [default=yes]
 > > }}}
 >
 > {{{--enable-geocallbacks=no}}} sets the flag {{{OMIT_GEOCALLBACKS}}}
 that does NOT define the geometry_callback functions (i.e.
 sqlite3_rtree_geometry_callback) within the spatialite library.
 >
 > So disabling the geometry callbacks in spatialite lib cannot make
 grass7-dev working again.

 forwarded from the spatialite-ML (and to the GRASS-dev-ML):

 {{{
 > in SpatiaLite? 3.0.1 (the version shipped with OSGeo4W) the name
 > of the flag is OMIT_GEOCALLBACKS, probably it was changed to
 > DISABLE_GEOMETRY_CALLBACKS in the last splite version.
 >

 there is absolutely no contradiction (no change) in this.
 reality is much more simple: OSGeo4W doesn't uses the canonical build
 scripts; it's based instead on the proprietary MSVC compiler.
 and in this environment canonical ./configure scripts are nicely
 unsupported at all.

 ./configure --enable-geocallbacks=[yes|no]

 this will automatically set as appropriate an internal C flag named
 OMIT_GEOCALLBACKS, and will silently set any Makefile as required.
 OSGeo4W skips at all the "abstract level" handled by the ./configure
 script, directly jumping to the "raw level" of Makefiles and C code;
 so the canonical --enable-geocallbacks or --disable-geocallbacks
 options are surely invisible from their own perspective, and they
 can simply interact with the OMIT_GEOCALLBACKS flag.


 >  So disabling the geometry callbacks in spatialite lib cannot make
 > grass7-dev working again.
 >
 > any idea?
 >

 looks like a grass7-dev specific problem; very probably some of their
 modules are still using the deprecated geo-callbacks methods, that
 are now disabled by default and that will be definitely removed from
 future versions of spatialite.
 correcting the C code so to switch from geo-callbacks to the most
 recent
 VirtualSpatialIndex interface is a very simple operation, just
 requiring
 to rewrite the SQL queries accessing the Spatial Index.
 Not at all a complex patch.

 bye Sandro
 }}}

-- 
Ticket URL: <http://trac.osgeo.org/osgeo4w/ticket/305#comment:26>
OSGeo4W <http://trac.osgeo.org/osgeo4w>
OSGeo4W is the Windows installer and package environment for the OSGeo stack.