Le mardi 03 mai 2016 19:50:11, Alan Stewart a écrit : > Even, > > The libspatialite code where the failure occurs is only executed when > spatialite is built with LOADABLE_EXTENSION undefined. Is there any > possibility that the new gpkg code depends on this being defined? > LOADABLE_EXTENSION does not appear anywhere in the GDAL source.
Alan, From what I see from spatialite code, spatialite_init_ex() is only defined if LOADABLE_EXTENSION is undefined (by spatialite own makefiles). LOADABLE_EXTENSION is undefined when libspatialite.so/.dll is built, and defined when mod_spatialite is built ( https://www.gaia- gis.it/fossil/libspatialite/wiki?name=mod_spatialite ). And GDAL needs spatialite_init_ex() to be defined when linking against new (>= 4.1.2) spatialite versions. I'm not sure what's wrong/particular with your sqlite and/or spatialite build, but there are several builds in the wild that work (MS4W, OSGeo4W, gisinternals). If you don't need spatialite, you can disable it when building GDAL. The GPKG driver doesn't absolutely require it. Spatialite provides processing functions, but for simple read/write scenarios, they are not needed. You can also dynamically disable spatialite loading by defining SPATIALITE_LOAD=NO as environmenet variable. Even > > Alan Stewart > Senior Software Engineer > TerraGo Technologies > 3200 Windy Hill Road, Suite 1550W > Atlanta, GA 30339 USA > O. +1 678.391.9615 > > www.terragotech.com > > -----Original Message----- > From: Even Rouault [mailto:even.roua...@spatialys.com] > Sent: Saturday, April 30, 2016 11:00 AM > To: gdal-dev@lists.osgeo.org > Cc: Alan Stewart > Subject: Re: [gdal-dev] GDAL 2.0.2 & gpkg woes > > On Friday 29 April 2016 14:07:52 Alan Stewart wrote: > > My debug build of ogr2ogr.exe fails in exactly the same way as my > > application code fails. Apparently there's some difference in how the > > new GPKG code uses spatialite or expects spatialite to be built? The > > same libspatialite DLL works with our GDAL 1.11.0 DLL, but fails with > > the new GDAL 2.0.2 DLL. > > Alan, > > Never heard of similar issues. But you could probably try to upgrade to the > latest version of sqlite in the 3.8.X series. And/or upgrade your > spatialite version to the latest stable 4.3.0a. Might be possible that the > changes between GDAL 1.11 and 2.0 have triggered an integration issue with > one of the sqlite/spatialite versions you use. > > Even > > > Alan Stewart > > Senior Software Engineer > > TerraGo Technologies > > 3200 Windy Hill Road, Suite 1550W > > Atlanta, GA 30339 USA > > O. +1 678.391.9615 > > > > www.terragotech.com > > > > _______________________________________________ > > gdal-dev mailing list > > gdal-dev@lists.osgeo.org > > http://lists.osgeo.org/mailman/listinfo/gdal-dev > > -- > Spatialys - Geospatial professional services http://www.spatialys.com -- Spatialys - Geospatial professional services http://www.spatialys.com _______________________________________________ gdal-dev mailing list gdal-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/gdal-dev
