[geos-devel] [postgis-devel] RFC6 - Require explicit configure to use the C++ API

Regina Obe lr at pcorp.us
Tue Oct 3 12:44:03 PDT 2017

After much heated argument on this mailing list and PostGIS IRC, none of the other PSC members seem interested in changing GEOS at all.

Hobu booed, strk didn't want to say anything, mloskot booed, pramsey was silent.

Dale and Keith ironically seemed to be the most agreeable folks using GEOS.

Hobu and Mloskot feel strongly that  GEOS C++ API is a major feature of GEOS and the key feature and if packagers feel strongly against allowing C++ API GEOS projects in the packages, 
they should stop shipping the libgeos++-dev so users trying to use those will not be able to compile said projects against  a packaged GEOS.

I have marked the RFC as failed so it's there, we know we officially discussed it,  and officially shot it down.


Sorry for this waste of everyone's time,


-----Original Message-----
From: geos-devel [mailto:geos-devel-bounces at lists.osgeo.org] On Behalf Of Sandro Santilli
Sent: Tuesday, October 03, 2017 2:32 PM
To: GEOS Development List <geos-devel at lists.osgeo.org>
Subject: Re: [geos-devel] [postgis-devel] RFC6 - Drop GEOS C++ API at GEOS 3.8

On Tue, Oct 03, 2017 at 10:33:51AM -0400, Regina Obe wrote:

> Is there a way to get rid of the shared C++ library and just have a C library or is that what you were talking about with the static  C++ library.

That's what I'm talking about with the static-only C++ library.
The C library would then _include_ (statically link to) the
C++ library.

I'm not sure about the consequences of that though (guess we'd need more symbols hiding or it could still be possible for different versions of the embedded C++ library to be confused during code execution).

geos-devel mailing list
geos-devel at lists.osgeo.org

More information about the geos-devel mailing list