Hi Benjamin, Neither way feels especially good for me but one or another should be selected if the aim is to develop Spatialite driver into a maintained extension. I understood that the statically linked standalone driver is painless for the end users, but how many different driver versions should be built and maintained for supporting Mac/Windows/and a few most common Linux brands , both 32 and 64 bit? Is it one for each combination?
You wrote that you will not try to build for anything else than OS X and I know that none of the core Geoserver developers work on Windows. On the other hand, building Spatialite with GEOS for Windows is somehow tricky if I have understood right what I have read from the Spatialite-users forum. Perhaps for this reason the Spatialite product builds ready-made mod_spatilite binaries for Windows which are downloadable with all the dependencies (http://www.gaia-gis.it/gaia-sins/windows-bin-x86-test/mod_spatialite-4.2.1-rc0-win-x86.7z or http://www.gaia-gis.it/gaia-sins/windows-bin-amd64-test/mod_spatialite-4.2.1-rc0-win-amd64.7z) Using these binaries (and updating mod_spatialite to later versions when they are released) is quite easy on Windows despite some dll-hell troubles which may arise. With some help from an OpenJUMP developer I have managed to update an old OpenJUMP plugin to use Spatialite 4.2.1-RC0 instead of Spatialite 2.x and one other user has managed to install it from http://latuviitta.org/downloads/OJ_SPLite_32-bit_lib_ext.zip and http://latuviitta.org/downloads/OJ_SPLite_64-bit_lib_ext.zip so I know that an out-of-the-box installation with mod_spatialite it is doable on Windows. However, mod_spatialite is not available for other platforms as downloadable binaries which leads to all the pain you have suffered. In conclusion, without being a programmer I have a feeling that maintaining Spatialite driver for all platforms would need some involvement and I guess that Geoserver developers will not take that workload without paying customers. Therefore I doubt there will be an official Spatialite driver with good support in near future. Personally I hope that somebody at least continues your work and builds your Spatialite driver fork for 64 bit Windows because Spatialite is the DB I use most nowadays. What do you think about GeoPackage and libgpkg https://bitbucket.org/luciad/libgpkg/src? -Jukka Rahkonen- Lähettäjä: Stadin, Benjamin [mailto:[email protected]] Lähetetty: 29. lokakuuta 2014 1:54 Vastaanottaja: GeoServer Mailing List List Aihe: Re: [Geoserver-users] New SpatiaLite JDBC fork Hi Jukka, Yes, I've considered this (I also came across this site). In general, the SQLite extension loading mechanism works very well. I've implemented some SQLite extensions before. The driver could be changed easily to use mod_spatialite instead of the static library. But I dislike one thing about mod_spatialite - the same reasons for which xerial decided to embed SQLite into the driver (authors of the SQLite JDBC library): Dynamic linkage and manual configurations are very error prone to the user with a JDBC driver. For an example, It took me some time to get all libraries right on my system. Some libs were absent or had a wrong version, or need to be recompiled some config option in a latest version changed and. It get's worse when a user has to figure what's wrong when the JDBC module just doesn't work - it's hard to debug even for developers. So in my opinion a JDBC driver must embed as much as possible and preferably work out of the box. I otherwise agree with the SpatiaLite developers when no Java / JNI is involved. - Ben Von: "Rahkonen Jukka (Tike)" <[email protected]<mailto:[email protected]>> Datum: Dienstag, 28. Oktober 2014 23:30 An: Benjamin Stadin <[email protected]<mailto:[email protected]>>, GeoServer Mailing List List <[email protected]<mailto:[email protected]>> Betreff: Re: [Geoserver-users] New SpatiaLite JDBC fork Hi Benjamin, Have you considered to make SpatiaLite driver so that SpatiaLite would be loaded as a dynamic extension https://www.gaia-gis.it/fossil/libspatialite/wiki?name=mod_spatialite? At least update to next SpatiaLite versions should be easier then because only the native "mod_spatialite" component needs to be updated. Or is there something in the Spatialite driver that would not work if Spatialite were loaded as an extension? -Jukka Rahkonen- ________________________________ Stadin, Benjamin wrote: Hi, The new SpatiaLite 4.2.1 driver is now working with Geoserver 2.6 on OS X. Please help to get this ported to other platforms as well. I've copy pasted an update to the previous spatialite documentation. It shouldn't be too hard to get it working on Windows as well, since the new Spatialite is based on autoconfig and there are not too many dependencies to resolve. I hope the driver will work stand-alone, it's linked statically agains all libraries. But I did not yet test for hidden linkages. OS X install instructions: * Download gt-jdbc-spatialite and install it to the WEB-INF/lib folder of Geoserver http://download.osgeo.org/webdav/geotools/org/geotools/jdbc/gt-jdbc-spatialite/12.0.1/ * Download the actual jdbc driver and install it also to WEB-INF/lib: https://github.com/benstadin/spatialite4-jdbc/tree/spatialite4/release The driver currently contains only the Mac-64 build. Regards Ben PS: The updated documentation (rough draft, done a bit in a hurry): Spatialite4 Output Format Documentation As prerequisite, we first need to build the appropriate libraries For Windows 64-bits we need: - minGW(with MSYS shell): http://sourceforge.net/projects/mingw/files/Automated%20MinGW%20Installer/mingw-get/ * Just download the lastest version. * Execute the installer. * In repository catalogues, check "Download lastest repository" * In select components select all options exept "MinGW Developer Toolkit" - PROJ.4 Library: #url = http://trac.osgeo.org/proj/ - GEOS Library: #url = http://trac.osgeo.org/geos/ - LIBICONV Library: #url = http://gnuwin32.sourceforge.net/packages/libiconv.htm (Only Binaries and Developer Files) And now we let's start to build libraries: #ref = http://www.gaia-gis.it/spatialite-2.4.0/mingw_how_to.html (Steps 1, 6, 8 and 9) - First of all, we need to execute MSYS.bat, located at /path/to/mingw/msys/1.0/msys.bat. - Building PROJ.4 : * just follow #ref = http://www.gaia-gis.it/spatialite-2.4.0/mingw_how_to.html#libproj - Building GEOS : * just follow #ref = http://www.gaia-gis.it/spatialite-2.4.0/mingw_how_to.html#libgeos - including LIBICONV : * just copy the ziped files (Binaries and Developer) into /path/to/minwg/msys/1.0/local Now we're ready to actually build SpatiaLite4 JDBC: - Install and configure (Check if the directory is in the PATH environment variable) Maven2 (or highter). #url = http://maven.apache.org/ - Install and configure (Check if the directory is in the PATH environment variable) Mercurial (hg). #url = http://mercurial.selenic.com - Wither git clone spatialite4-jdbc, or simply download the repository ("Download ZIP") from Github (spatialite4 branch): * https://github.com/benstadin/spatialite4-jdbc/tree/spatialite4 - Go inside the root of spatialite4-jdbc and run: * make - When finished, go inside "target" directory and search for "spatialite4-jdbc-($version)-SNAPSHOT.jar" (This one is the JDBC for our SO). The makefile builds and configures both SpatiaLite and SQLite, and runs a test after successful build. If all tests pass, everything should be fine and you can copy the .jar file to it's destined location.
------------------------------------------------------------------------------
_______________________________________________ Geoserver-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-users
