Re: [geos-devel] RFC6 - Drop GEOS C++ API at GEOS 3.8

On Sun, Oct 01, 2017 at 11:19:48PM -0400, Regina Obe wrote: > Getting back to your option with ./configure, would it be possible to only > allow enabling of the C++ API if it's being built as a static library. I > think our main issue is when it's shared. I was thinking of a more explicit

Re: [geos-devel] RFC6 - Drop GEOS C++ API at GEOS 3.8

Kurt, Thanks for responding. It's still on the table. I just wanted to air out the issues. I was referring to install of headers. Sandro et. al, Getting back to your option with ./configure, would it be possible to only allow enabling of the C++ API if it's being built as a

Re: [geos-devel] RFC6 - Drop GEOS C++ API at GEOS 3.8

-1 (non-PSC). Please do not drop the C++ the C++ API. Some folks (e.g. me at Google) statically link GEOS and ABI compatibility is not an issue. Every build is a complete system. Working with C APIs is far harder. We end up having to wrap a C++ API back over C APIs. But do note that I don't

[geos-devel] RFC6 - Drop GEOS C++ API at GEOS 3.8

Okay I have created an RFC6 to officially drop GEOS C++ starting at GEOS 3.8 (so as soon as we release GEOS 3.7 (which should be next month), and flip the switch, we drop the C++ headers as well so developers won't be tempted to use them. https://trac.osgeo.org/geos/wiki/RFC6 As Bas said

Re: [geos-devel] [postgis-devel] GEOS C++ API deprecated? (was: PostGIS 2.5 what should be minimum requirements?)

On 1 October 2017 at 22:17, Sebastiaan Couwenberg wrote: > On 10/01/2017 10:05 PM, Mateusz Loskot wrote: >> On 1 October 2017 at 21:47, Sebastiaan Couwenberg wrote: >>> On 10/01/2017 09:33 PM, Mateusz Loskot wrote: Unless, Sandro, your aim is to

Re: [geos-devel] [postgis-devel] GEOS C++ API deprecated? (was: PostGIS 2.5 what should be minimum requirements?)

On 1 October 2017 at 22:17, Sandro Santilli wrote: > On Sun, Oct 01, 2017 at 10:05:43PM +0200, Mateusz Loskot wrote: > >> I only ask Sandro, as the GEOS leader/PSC member to answer one question: >> >> Do you plan to practically deprecate GEOS C++ API and stop installing >> GEOS C++

Re: [geos-devel] [postgis-devel] GEOS C++ API deprecated? (was: PostGIS 2.5 what should be minimum requirements?)

On Sun, Oct 01, 2017 at 10:05:43PM +0200, Mateusz Loskot wrote: > I only ask Sandro, as the GEOS leader/PSC member to answer one question: > > Do you plan to practically deprecate GEOS C++ API and stop installing > GEOS C++ headers? I don't have such plan, but it could be an idea to make it

Re: [geos-devel] [postgis-devel] GEOS C++ API deprecated? (was: PostGIS 2.5 what should be minimum requirements?)

On 10/01/2017 10:05 PM, Mateusz Loskot wrote: > On 1 October 2017 at 21:47, Sebastiaan Couwenberg wrote: >> On 10/01/2017 09:33 PM, Mateusz Loskot wrote: >>> Unless, Sandro, your aim is to eventually mark C++ API deprecated >>> and stop installing C++ API libraries and

Re: [geos-devel] [postgis-devel] GEOS C++ API deprecated? (was: PostGIS 2.5 what should be minimum requirements?)

On 1 October 2017 at 21:47, Sebastiaan Couwenberg wrote: > On 10/01/2017 09:33 PM, Mateusz Loskot wrote: >> Unless, Sandro, your aim is to eventually mark C++ API deprecated >> and stop installing C++ API libraries and headers. >> >> That will require RFC and that is what I'm

Re: [geos-devel] GEOS C++ API deprecated? (was: PostGIS 2.5 what should be minimum requirements?)

On 1 October 2017 at 20:47, Sandro Santilli wrote: > On Sat, Sep 30, 2017 at 09:26:42PM +0200, Mateusz Loskot wrote: >> /topic changed >> /cc geos-devel >> >> On 30 September 2017 at 20:47, Greg Troxel wrote: > >> > ### Using the C++ interface (discouraged) >> >

Re: [geos-devel] GEOS C++ API deprecated? (was: PostGIS 2.5 what should be minimum requirements?)

On Sat, Sep 30, 2017 at 09:26:42PM +0200, Mateusz Loskot wrote: > /topic changed > /cc geos-devel > > On 30 September 2017 at 20:47, Greg Troxel wrote: > > ### Using the C++ interface (discouraged) > > > > NB: The C++ interface should not be used directly; the GEOS project