From 921498671fafa4a82cbb19b6da9df30ff5d02056 Mon Sep 17 00:00:00 2001 From: Regina Obe Date: Sat, 21 Jan 2012 01:31:52 +0000 Subject: [PATCH] update build extensions to include the make comments if building from source repo and also that it requires a separate compile step (until #1490) git-svn-id: http://svn.osgeo.org/postgis/trunk@8898 b70326c6-7e19-0410-871a-916f4a2858ee --- doc/installation.xml | 19 +++++++++++++++++-- extensions/README | 29 ++++++++++++++++++++++++++--- 2 files changed, 43 insertions(+), 5 deletions(-) diff --git a/doc/installation.xml b/doc/installation.xml index 7f8e690da..14dcb8494 100644 --- a/doc/installation.xml +++ b/doc/installation.xml @@ -539,9 +539,24 @@ tar -xvzf postgis-&last_release_version;.tar.gz Building PostGIS Extensions and Deploying them - The PostGIS extensions which is usable for PostgreSQL 9.1+, should be automatically installed if you are built against - PostgreSQL 9.1+. + The PostGIS extensions which is usable for PostgreSQL 9.1+, can be built by cding into the extension folders and doing a make install. + This will be an automated process in the future when PostGIS is compiled against a 9.1 build and fully integrated int ot he build process. + If you are building from souce repository, you need to build the function descriptions first with: + make comments + Building the comments is not necessary if you are building from a tar ball since these are packaged pre-built with the tar ball already. + Next build the extensions and install them. + cd extensions +cd postgis +make clean +make +make install +cd .. +cd postgis_topology +make clean +make +make install + The extension files will always be the same for the same version of PostGIS regardless of OS, so it is same as long as you have the PostGIS binaries already installed on your servers, to copy over the extension files. If you want to install the extensions manually on a separate server different from your development, diff --git a/extensions/README b/extensions/README index 1b7655803..1d5fbd445 100644 --- a/extensions/README +++ b/extensions/README @@ -3,9 +3,25 @@ to allow postgis modules to be installed using standard PostgreSQL 9.1+ CREATE EXTENSION syntax -To use: first make install regular PostGIS. +To use: first make install regular PostGIS. Also make sure to make the comments +if you are building from teh source repository +since the extensions package the postgis function descriptions. +make comments + +Makign the comments is not necessary if you are building +from the tar balls since the tar balls have +the various postgis_comments.sql, topology_comments.sql, +and raster_comments.sql already built. + +Then: +cd extensions/postgis +make install +cd .. +cd extensions/postgis_topology +make install + These should automatically get installed in share/extension folder of -PostGIS if you compiled against PostgreSQL 9.1 +PostgreSQL 9.1. Then in your PostgreSQL database run CREATE EXTENSION postgis; @@ -16,4 +32,11 @@ The dependency logic should warn if you try to install postgis_topology without postgis or try to drop postgis without first droping postgis_topology. -You will also not be able to drop any postgis functions installed by the extension. \ No newline at end of file +You will also not be able to drop any postgis functions installed by the extension. +If you want to manually install the extensions from one server to another +, just copy over the + +extensions/postgis: postgis.control, sql/* +extension/postgis_topoloyg postgis_topology.control,sql/* + +files into your PostgreSQL/share/extension folder. \ No newline at end of file -- 2.40.0