View Ticket
Not logged in
Ticket Hash: adbde604ba08971a134d02ec6df78789b5c2bfec
Title: libspatialite does not support newer versions of liblwgeom
Status: Closed Type: Code_Defect
Severity: Cosmetic Priority: Zero
Subsystem: Resolution: Works_As_Designed
Last Modified: 2018-01-08 05:03:48
Version Found In: 4.3.0a
User Comments:
anonymous added on 2018-01-07 16:15:55:
libspatialite will not compile against current versions of liblwgeom due to changes in the lw_vasprintf function (renamed to sqlite3_vmprintf).

The following patch fixes the issue: https://gist.githubusercontent.com/rundel/e64e184f0d2fcceaf14ef011b3432a07/raw/4371005dc648e0415d8118872f344c03d0ccc3d5/libspatialite.patch

The fix is based on the discussion posted here: https://groups.google.com/forum/#!msg/spatialite-users/LuFirW-60q4/3ccGcWcDDgAJ

mj10777 added on 2018-01-08 05:03:48:

LWGEOM has been replaced by RTTOPO since April 2016, see:

https://groups.google.com/forum/#!searchin/spatialite-users/rttopo%7Csort:date/spatialite-users/MlXsPU0ZMYw/F377fpCsNwAJ

As stated in the 'bye bye LWGEOM' message, the switch was needed to remove the PostGIS dependency, since a Spatialite support for Topology has been added which does not always matches with PostGIS approach.

Also, sudden, unannounced API changes were made by the PostGIS team to LWGEOM, as you noted in your comment, which caused problems.

LWGEOM was originally funded by Tuscany Region to be used as a common interface for both systems, but due to the changed attitude of the PostGIS team, this was no longer possible.

See:
Andrea Peri, 'A letter to the Postgis Developers and Packagers', 18 Oct 2015
at:
https://lists.osgeo.org/pipermail/postgis-devel/2015-October/thread.html

The lack of conciseness in this matter lead to the switch to RTTOPO.

A further advantage to this change, is that libspatialite can be ported of systems like android, which before was not possible due to the PostGIS/Postgres dependency.