[postgis-devel] liblwgeom.so

[Paul Ramsey]

I'm really having a hard time wrapping my head around the benefits of
this change, can someone enumerate them?

On the con side, so far we have a more complicated build and the
potential for DLL hell. I note my shp2pgsql and pgsql2shp utilities
are showing new the external dependencies now, so they aren't
statically linked[1]  Fortunately, postgis-2.0.so is statically linked
[2] small blessings.

Can someone enumerate all the positives this change to now having an
extra library installed is bringing us? If someone wants a C geometry
abstraction there's GEOS. If they want a feature abstraction that
wraps GEOS and provides reprojection, there's OGR. What's the benefit
to moving liblwgeom into the system?

P.


[1]
pramsey$ otool -L shp2pgsql
shp2pgsql:
	/System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
(compatibility version 150.0.0, current version 550.43.0)
	/usr/local/lib/liblwgeom-2.0.0SVN.dylib (compatibility version 0.0.0,
current version 0.0.0)
	/usr/local/lib/libgeos_c.1.dylib (compatibility version 8.0.0,
current version 8.3.0)
	/usr/local/lib/libgeos-3.2.3.dylib (compatibility version 0.0.0,
current version 0.0.0)
	/usr/local/lib/libproj.0.dylib (compatibility version 7.0.0, current
version 7.6.0)
	/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current
version 125.2.11)
	/opt/local/lib/libintl.8.dylib (compatibility version 10.0.0, current
version 10.1.0)
	/opt/local/lib/libiconv.2.dylib (compatibility version 8.0.0, current
version 8.1.0)


[2]
pramsey$ otool -L postgis-2.0.so
postgis-2.0.so:
	/usr/local/lib/libgeos_c.1.dylib (compatibility version 8.0.0,
current version 8.3.0)
	/usr/local/lib/libproj.0.dylib (compatibility version 7.0.0, current
version 7.6.0)
	/opt/local/lib/libxml2.2.dylib (compatibility version 10.0.0, current
version 10.8.0)
	/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current
version 125.2.11)