changed then it also triggers a (complete) rebuild of PostGIS.
Note as documented in #447 this is an over-cautious approach since it rebuilds
all of PostGIS if liblwgeom changes, but at least its a starting point and
does actually solve the case whereby a user updates liblwgeom but doesn't
force a rebuild of PostGIS.
git-svn-id: http://svn.osgeo.org/postgis/trunk@7571
b70326c6-7e19-0410-871a-
916f4a2858ee
datadir=/share
endif
+# Make all PostGIS objects depend upon liblwgeom, so that if an underlying
+# change is made, a PostGIS rebuild is triggered.
+$(PG_OBJS): ../liblwgeom/liblwgeom.a
# Borrow the $libdir substitution from PGXS but customise by adding the version number
%.sql: %.sql.in