[postgis-devel] Re: [PostGIS] #160: prefix not recognized in 1.4.0SVN

[Kevin Neufeld]

An (albeit small) issue I see with this is:

The autobuild environment I set up is organized in such a way that I can have various versions of the PostGIS 
dependences pre-built (GEOS, Proj, Postgresql, etc.).  That way I can build PostGIS against various configurations for 
testing.

Being tied to PGXS means that the same can never be said about liblwgeom - it'll be tied directly to a particular 
PostgreSQL installation. If someone wanted to build a project that relies on liblwgeom, building various versions will be:
- configure
- make
- find liblwgeom.so and related links
- manually copy libs to particular installation directory
instead of the typical make && make install.

Not a big deal by any means, but I guess that's another reason why it might be a good idea to have liblwgeom as a 
separate project.

-- Kevin


PostGIS wrote:
> #160: prefix not recognized in 1.4.0SVN
> -----------------------+----------------------------------------------------
>   Reporter:  kneufeld  |       Owner:  mcayland     
>       Type:  defect    |      Status:  new          
>   Priority:  low       |   Milestone:  postgis 1.4.0
>  Component:  postgis   |     Version:               
> Resolution:            |    Keywords:               
> -----------------------+----------------------------------------------------
> Comment (by mcayland):
> 
>  I'm not convinced that this is necessarily a bug; the new version of
>  configure has NO knowledge of any of the installation paths since this is
>  handled entirely by PGXS, and for a good reason. The location of the sql
>  files in particular has tended to change from version to version.
> 
>  There may be an argument for extending PGXS so that --prefix specifies a
>  new root directory rather than an a prefix (which is perhaps what Kevin
>  was expecting to see?). But if you're interested in this as a feature,
>  you'd need to chase it up with the PGSQL folks.
> 
> 
>  ATB,
> 
>  Mark.
>