[postgis-devel] For PostGIS 2.2 moving forward make liblwgeom compatible between micro releases

Paragon Corporation lr at pcorp.us
Mon Jul 20 08:31:32 PDT 2015


I'd be even happier with that, but I thought the executables for some reason couldn't be statically linked.

 

I think my postgis and rtpostgis PostgreSQL libraries still are (have to double-check), but since the mingw fix change, I no longer have statically linked executables.

 

Thanks,

Regina

 

 

From: Paul Ramsey [mailto:pramsey at cleverelephant.ca] 
Sent: Monday, July 20, 2015 11:05 AM
To: PostGIS Development Discussion <postgis-devel at lists.osgeo.org>; Paragon Corporation <lr at pcorp.us>
Subject: Re: [postgis-devel] For PostGIS 2.2 moving forward make liblwgeom compatible between micro releases

 

Can we do the opposite and more aggressively statically link postgis and all output programs, so packagers don’t need to include liblwgeom with postgis packages?

 

-- 
Paul Ramsey
http://cleverelephant.ca

http://postgis.net 

 

On July 20, 2015 at 7:36:50 AM, Paragon Corporation (lr at pcorp.us <mailto:lr at pcorp.us> ) wrote:

I would like to push this as a necessary thing and also require the library 
does not change name with each micro release of postgis. 

I know now that I am stuck with a dynamic dll for liblwgeom (before in 2.1 I 
was able to live obliviously to these concerns until this change - 
https://trac.osgeo.org/postgis/ticket/3170 ) . 

The fact the library changes name with each micro (and api sometimes 
changes) is a packaging nightmare. 

Can we at least get this fixed in 2.2 and promise to not change the api with 
each micro release? 

https://trac.osgeo.org/postgis/ticket/2278 

Thanks, 
Regina 


_______________________________________________ 
postgis-devel mailing list 
postgis-devel at lists.osgeo.org <mailto:postgis-devel at lists.osgeo.org>  
http://lists.osgeo.org/cgi-bin/mailman/listinfo/postgis-devel 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-devel/attachments/20150720/512856cd/attachment.html>


More information about the postgis-devel mailing list