<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>Glad it wasn't totally wasted effort and thanks for being so agreeable and explaining your use. <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'> I also apologize for mistyping your name.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>Thanks,<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>Regina<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal style='margin-left:.5in'><b><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'>From:</span></b><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'> geos-devel [mailto:geos-devel-bounces@lists.osgeo.org] <b>On Behalf Of </b>Kurt Schwehr<br><b>Sent:</b> Tuesday, October 03, 2017 6:08 PM<br><b>To:</b> GEOS Development List <geos-devel@lists.osgeo.org><br><b>Subject:</b> Re: [geos-devel] [postgis-devel] RFC6 - Require explicit configure to use the C++ API<o:p></o:p></span></p><p class=MsoNormal style='margin-left:.5in'><o:p> </o:p></p><div><p class=MsoNormal style='margin-left:.5in'>I don't consider it a waste of time. Thank you for taking the time for the RFC and especially for the summary. <o:p></o:p></p></div><div><p class=MsoNormal style='margin-left:.5in'><o:p> </o:p></p><div><p class=MsoNormal style='margin-left:.5in'>On Oct 3, 2017 12:44 PM, "Regina Obe" <<a href="mailto:lr@pcorp.us">lr@pcorp.us</a>> wrote:<o:p></o:p></p><blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in'><p class=MsoNormal style='margin-left:.5in'>After much heated argument on this mailing list and PostGIS IRC, none of the other PSC members seem interested in changing GEOS at all.<br><br>Hobu booed, strk didn't want to say anything, mloskot booed, pramsey was silent.<br><br>Dale and Keith ironically seemed to be the most agreeable folks using GEOS.<br><br>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,<br>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.<br><br>I have marked the RFC as failed so it's there, we know we officially discussed it, and officially shot it down.<br><br><a href="https://trac.osgeo.org/geos/wiki/RFC6" target="_blank">https://trac.osgeo.org/geos/wiki/RFC6</a><br><br>Sorry for this waste of everyone's time,<br><br>Regina<br><br><br>-----Original Message-----<br>From: geos-devel [mailto:<a href="mailto:geos-devel-bounces@lists.osgeo.org">geos-devel-bounces@lists.osgeo.org</a>] On Behalf Of Sandro Santilli<br>Sent: Tuesday, October 03, 2017 2:32 PM<br>To: GEOS Development List <<a href="mailto:geos-devel@lists.osgeo.org">geos-devel@lists.osgeo.org</a>><br>Subject: Re: [geos-devel] [postgis-devel] RFC6 - Drop GEOS C++ API at GEOS 3.8<br><br>On Tue, Oct 03, 2017 at 10:33:51AM -0400, Regina Obe wrote:<br><br>> 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.<br><br>That's what I'm talking about with the static-only C++ library.<br>The C library would then _include_ (statically link to) the<br>C++ library.<br><br>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).<br><br>--strk;<br>_______________________________________________<br>geos-devel mailing list<br><a href="mailto:geos-devel@lists.osgeo.org">geos-devel@lists.osgeo.org</a><br><a href="https://lists.osgeo.org/mailman/listinfo/geos-devel" target="_blank">https://lists.osgeo.org/mailman/listinfo/geos-devel</a><br><br>_______________________________________________<br>geos-devel mailing list<br><a href="mailto:geos-devel@lists.osgeo.org">geos-devel@lists.osgeo.org</a><br><a href="https://lists.osgeo.org/mailman/listinfo/geos-devel" target="_blank">https://lists.osgeo.org/mailman/listinfo/geos-devel</a><o:p></o:p></p></blockquote></div></div></div></body></html>