Re: [geos-devel] 3.5 not built by Debbie?

Sorry it wasn't part of the view. I just added to the GEOS view so now you should see it. -Original Message- From: Mateusz Loskot [mailto:mate...@loskot.net] Sent: Wednesday, June 08, 2016 3:59 AM To: Mateusz Loskot ; geos-devel@lists.osgeo.org; Paragon Corporation

Re: [geos-devel] RFC 5: C++11 Compilation Mode

As long as this is just for GEOS trunk+ Geos 3.7+, I'm fine with the change +1 All stable branches should of course stay as is. FWIW for GEOS I compile under mingw64 32-bit (GCC 4.8.1) and 64-bit (GCC 4.8.3) ) using CMake and am slowly migrating to GCC 4.9.2 So I don't think this will

Re: [geos-devel] Ready to switch from SVN to GIT ?

Mat, Can you state things you like about github over gogs. I feel like I don't commit enough to have authority on the matter and so your opinion should matter more. I don't know why it bugs me so much about reliance on GitHub, but it does. Perhaps because I feel it's a free lunch that may

Re: [geos-devel] Ready to switch from SVN to GIT ?

Mat, >> Then again I understand that maintaining an infrastructure like Gogs >> requires someone willing to do it or get paid for it, so that's even less of >> a free lunch but does give us more control over our destiny and how we >> integrate with other pieces of our infrastructure. > At

Re: [geos-devel] Ready to switch from SVN to GIT ?

Here are my thoughts mostly in-line with strk and speaking from my selfish point of view. On Thu, Apr 06, 2017 at 06:41:27PM +0200, Mateusz Loskot wrote: >> >> Drone is rather an interesting addition, not something to rely on, from my >> POV. >> It does not support builds on Windows. I'm not

Re: [geos-devel] Ready to switch from SVN to GIT ?

> Another problem w/ maintaining OSGeo-hosted infrastructure is lack of admins > even remotely interested in getting a contract. > Year ago Sandro, if I'm correct, pioneered sysadmins contracting for OSGeo > (https://lists.osgeo.org/pipermail/sac/2016-May/007032.html). > Year later... I have

[geos-devel] FOSS4G 2017 Boston Code Sprint

. If you'd like to attend, please add your name to the list below so we can plan accordingly. Also feel free to spread the word. https://wiki.osgeo.org/wiki/FOSS4G_2017_Code_Sprint#Code_Sprint Thanks, Regina Obe Boston LOC Committee member ___ geos

Re: [geos-devel] MOTION to accept this patch [geos] Emit a warning at compile time about C++ API being unstable (#14) - Summarize of votes

eos-devel@lists.osgeo.org> Subject: Re: [geos-devel] MOTION to accept this patch [geos] Emit a warning at compile time about C++ API being unstable (#14) On Wed, Oct 04, 2017 at 10:39:08AM -0400, Regina Obe wrote: > Can all PSC folks vote if this is agreeable. This will be done for

Re: [geos-devel] MOTION to accept this patch [geos] Emit a warning at compile time about C++ API being unstable (#14) - PASSES

e around me. Kinda lonely, really. On Thu, Oct 05, 2017 at 02:35:30AM -0400, Regina Obe wrote: > The MOTION for geos 3.7.0 is to put a warning in the Geometry.h header > file that will show whenever a user compiles a project source against > the GEOS C++ API. > With the intenti

Re: [geos-devel] Thoughts on Backporting the emit warning message to GEOS 3.6 and GEOS 3.5

Slight correction I meant "would be subjected to the warning if they are compiling source code that uses the C++ API." -Original Message----- From: Regina Obe [mailto:l...@pcorp.us] Sent: Friday, October 06, 2017 5:04 PM To: 'GEOS Development List' <geos-devel@lists.osgeo

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

. Thanks, Regina _ 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

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

I've revised the RFC6 so hopefully it's more agreeable to everyone. https://trac.osgeo.org/geos/wiki/RFC6 Perhaps in future when we have the manpower or funding to whole-heartedly support ABI compatibility for the C++ API as well, we can lift this guard. Thanks, Regina

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

>> On 10/03/2017 07:37 PM, Howard Butler wrote: >> What if we were to do the same thing with GDAL -- take away GDAL's C++ API >> which you were not supposed to use, but we put it out there anyway, because >> it was inconvenient for some of the open source packaging systems? Not >> possible

[geos-devel] GEOS 3.7.0 beta end this week

strk, You think we can have a beta end this week or you still working on stuff. I volunteer to do the release. Was just waiting for you last time. Thanks, Regina ___ geos-devel mailing list geos-devel@lists.osgeo.org

Re: [geos-devel] GEOS 3.7.0 beta end this week

> BTW: /view/GEOS/job/GEOS_Master/buildWithParameters exists > /view/GEOS/job/GEOS_Branch_3.6/buildWithParameters does not shouldn't it exist ? > --strk; I see it https://debbie.postgis.net:444/view/GEOS/job/GEOS_Branch_3.6/ I deleted all the old trunks on Winnie. I see it on Debbie

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

and I think that does make sense for PostGIS. On Sun, Oct 1, 2017 at 7:49 PM, Regina Obe <l...@pcorp.us <mailto:l...@pcorp.us> > wrote: 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 f

[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] RFC6 - Drop GEOS C++ API at GEOS 3.8

On 2 October 2017 at 09:30, Bas Couwenberg wrote: > On 2017-10-02 09:13, Mateusz Loskot wrote: >>> >>> As Bas said already it causes packagers headaches. >> >> So, the solution is to take the toys away from the kids... >> >> >> Please help us understand your point of view.

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

Per strk's requiest, here is my revised RFC. https://trac.osgeo.org/geos/wiki/RFC6 -Original Message- From: Regina Obe [mailto:l...@pcorp.us] Sent: Tuesday, October 03, 2017 10:34 AM To: 'GEOS Development List' <geos-devel@lists.osgeo.org> Subject: RE: [geos-devel] [postgis

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

, 2017 at 09:02:38PM -0400, Regina Obe wrote: > I've revised the RFC6 so hopefully it's more agreeable to everyone. > https://trac.osgeo.org/geos/wiki/RFC6 That RFC introduces a configure-time switch to enable installing C++ header, but doesn't mention installing C++ library, sounds incons

[geos-devel] GEOS 3.7.0 release in 2 weeks

. Let me know if anyone has issue with that or if they really want an RC first. I've still got a couple more tickets to push to GEOS 3.8 milestone. Thanks, Regina Obe GEOS PSC member ___ geos-devel mailing list geos-devel@lists.osgeo.org https

Re: [geos-devel] GEOS 3.7.0 release in 2 weeks

> "Regina Obe" <l...@pcorp.us> writes: >> Let me know if anyone has issue with that or if they really want an RC >> first. > From the packaging viewpoint, I'd like an RC (which preferably unpacks to the same pathname as the file, so that one can just change

Re: [geos-devel] GEOS 3.7.0 release in 2 weeks

wants to do some major refactoring and up the required GCC to 4.8. We might want to even consider calling the next version GEOS 4.0 just for that. Mat -- thoughts? Thanks, Regina -Original Message- From: Regina Obe [mailto:l...@pcorp.us] Sent: Friday, September 01, 2017 10:26 AM

Re: [geos-devel] GEOS 3.7.0 release in 2 weeks

Roger, I believe most of the changes in GEOS 3.7.0 are bug fixes too involved to backport to GEOS 3.6. There are some new features but not all that many. If I were to release an alpha, I think it would be setting a precedent since I don't think an alpha has ever been released for GEOS. At

Re: [geos-devel] git hooks updated to hit Winnie and Debbie web hooks

Strk, Right now the job names are For Debbie: GEOS_Master GEOS_Branch_3.2 Thru GEOS_Branch_3.6 For Winnie: I got to convert the older branches and fix them, but she has Hers are not that consistent, so I got to rename the branches so you only got to worry about one set of names. Assume

Re: [geos-devel] Accompanying .editorconfig with .gitattributes?

I'm fine with that. +1 I think as long as we don't have SVN in mix anymore that should behave right. -Original Message- From: geos-devel [mailto:geos-devel-boun...@lists.osgeo.org] On Behalf Of Mateusz Loskot Sent: Tuesday, August 29, 2017 11:56 AM To: geos-devel@lists.osgeo.org

Re: [geos-devel] Accompanying .editorconfig with .gitattributes?

Forget my +1 earlier. -1 one I change to -1 :) -Original Message- From: geos-devel [mailto:geos-devel-boun...@lists.osgeo.org] On Behalf Of Sandro Santilli Sent: Tuesday, August 29, 2017 4:10 PM To: GEOS Development List Subject: Re: [geos-devel]

[geos-devel] MOTION to accept this patch [geos] Emit a warning at compile time about C++ API being unstable (#14)

Can all PSC folks vote if this is agreeable. This will be done for GEOS 3.7 and above. Feedback from others is welcome as well. This GEOS patch will display a warning in the Geometry.h header which appears during compile time whenever the C++ API is used to compile a projects source, unless

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

:44 PM, "Regina Obe" <l...@pcorp.us <mailto:l...@pcorp.us> > wrote: 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

Re: [geos-devel] RFC6 - Discourage use of C++ API by requiring a configure switch to install the c++ headers and SDK

Dale, Thanks. Yes I missed this note. I've revised the subject line above to make it clear what my proposal was changed to after input from you and Kurt. The new proposal - https://trac.osgeo.org/geos/wiki/RFC6 is to keep the C++ API but require people building to have a

Re: [geos-devel] Thoughts on Backporting the emit warning message to GEOS 3.6 and GEOS 3.5

opment List <geos-devel@lists.osgeo.org> Subject: Re: [geos-devel] Thoughts on Backporting the emit warning message to GEOS 3.6 and GEOS 3.5 Sandro Santilli <s...@kbt.io> writes: > On Fri, Oct 06, 2017 at 05:03:58PM -0400, Regina Obe wrote: >> I'm only softly proposing

Re: [geos-devel] GIT repo url updated

strk, I'm so proud of you. You kept your cool and answered well. I can't say I would have handled Hobu's negativity as well. Looking forward to using gitea more. Thanks for all the hard work. Experimentation is very important to explore new avenues of working. We must not all follow the

Re: [geos-devel] Alternative licensing for GEOS

I personally would be okay with that. From: geos-devel [mailto:geos-devel-boun...@lists.osgeo.org] On Behalf Of Paul Ramsey Sent: Thursday, November 09, 2017 11:43 AM To: GEOS Development List Subject: Re: [geos-devel] Alternative licensing for GEOS Just

Re: [geos-devel] Alternative licensing for GEOS

He would have been faster if he wasn't in New Zealand :) Damn we lost the opportunity to change the license while he was asleep. From: geos-devel [mailto:geos-devel-boun...@lists.osgeo.org] On Behalf Of Howard Butler Sent: Wednesday, November 08, 2017 3:51 PM To: GEOS Development List

Re: [geos-devel] Motion: Approve Commit Access for Kurt Schwehr

+1 > -Original Message- > From: geos-devel [mailto:geos-devel-boun...@lists.osgeo.org] On Behalf Of > Howard Butler > Sent: Wednesday, June 06, 2018 8:48 AM > To: GEOS Development List > Subject: [geos-devel] Motion: Approve Commit Access for Kurt Schwehr > > Dear PSC, > > > Kurt has

[geos-devel] GEOS 3.7.0alpha release tomorrow

I had already flipped the version on GEOS to 3.7.0alpha and I just tested my experimental tagging. I'm planning to officially tag GEOS 3.7.0alpha tomorrow, anyone have issue with that? Again this is not quite a feature freeze, but just to get our machinery rolling and it will be the first tag

[geos-devel] PSC Vote: Move GEOS github out of OSGeo org and Back on Its own Org

As stated in my previous rant, I'd like to move https://github.com/OSGeo/geos To https://github.com/libgeos Per ticket I discovered travis is no longer enabled. https://trac.osgeo.org/geos/ticket/883 This would serve a couple of purposes 1) If we use travis, we will not be eating up

[geos-devel] Tickets that can be pushed / closed

I'd like to release GEOS 3.7.0beta1 sometime next week. Before I do, I want all changes that may incur introduction of new/change to function signatures to be in place before then. Here is list of open tickets for 3.7.0 https://trac.osgeo.org/geos/query?status=assigned=new=reopened =3.7.0 Some

[geos-devel] GEOS 3.7.0alpha is released

The GEOS development team is pleased to release the 3.7.0alpha version. Source download: http://download.osgeo.org/geos/geos-3.7.0alpha.tar.bz2 The following changes are in place since the 3.6 major release - New things: - CAPI: GEOSDistanceIndexed (#795, Dan Baston)

[geos-devel] PSC Vote release of GEOS 3.7.0alpha in 1-2 weeks

I'd like to propose that we do an alpha release of GEOS 3.7.0alpha in about 1-2 weeks. I know both Dan Baston and Even Rouault are working on things they'd like to get in. I'm okay with everything not in before alpha release, but read by beta. Part of the reason I want to do this is just to get

[geos-devel] Motion: Approve Commit Access for Kurt Schwehr - PASSED

> I have read RFC2 and agree to the terms. > Thanks!! > -kurt > schwehr at gmail / schwehr at google.com Great welcome aboard Kurt. I've given you access to the repo so you should be able to push thru your pull requests and commit directly. Let me know if you have problems. Thanks, Regina

[geos-devel] GEOS 3.7.0beta1 is released

The GEOS development team is pleased to release the 3.7.0beta1 version. Source download: http://download.osgeo.org/geos/geos-3.7.0beta1.tar.bz2 - New things: - CAPI: GEOSDistanceIndexed (#795, Dan Baston) - CAPI: GEOSCoordSeq_isCCW (#870, Dan Baston) - CAPI: GEOSGeom_getXMin,

Re: [geos-devel] Motion: Approve Commit Access for Kurt Schwehr

Looks like most folks in PSC have given Kurt Schwehr a thumbs up to be added to the team and no minuses. Before we consider the motion passed, Kurt, can you look over the below and see if you agree to the terms. I just updated to reference GIT instead of SVN.

[geos-devel] Geos 3.7.0beta1 release planned this Monday

I'm planning to release Geos 3.7.0beta1 this coming Monday. At that point I expect no more API changes. By that I mean only bug fixes, performance enhancements will be allowed. No new functions. Please speak up if you have issues with that. Since my last email discussing the open items, I

[geos-devel] Plan to release 3.6.3, 3.5.2, and 3.7.0beta2 in less than a week

I'm planning to release GEOS 3.6.3, 3.5.2, and 3.7.0beta2 in less than a week. Let me know if anyone has issue with this. Thanks, Regina ___ geos-devel mailing list geos-devel@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/geos-devel

[geos-devel] GEOS 3.6.3 and GEOS 3.7.0beta2 released

The GEOS development team is pleased to release the 3.7.0beta2 version. https://download.osgeo.org/geos/geos-3.7.0beta2.tar.bz2 Change Log: https://trac.osgeo.org/geos/browser/git/NEWS?rev=3.7.0beta2 We are planning to have GEOS 3.7.0 out before September. And GEOS 3.6.3

Re: [geos-devel] GEOS 3.7.0rc1 release

I asked Sebastian the same thing. He said it's needed in configure script to escape the [] as I recall. From: Greg Troxel [mailto:g...@lexort.com] Sent: Monday, August 20, 2018 4:39 PM To: Regina Obe Cc: 'GEOS Development List' Subject: RE: [geos-devel] GEOS 3.7.0rc1 release I believe

Re: [geos-devel] GEOS 3.7.0rc1 release

nor/patch. The sed > expression throws an error with NetBSD's sed, and gives an answer that > seems wrong with gsed. The use of extra [] just inside the () doesn't seem > right. > > Perhaps there should be instead of patch, patch and rc variables, with rc > being empty in rele

Re: [geos-devel] GEOS 3.7.0rc1 release

nge, but looking in NEWS, these are not mentioned. > [Regina Obe] I think it's for Frechet distance and was an early on change for 3.7 that way down in the news in the "What's new in 3.7" so will be in final release notes. Though those should have been there for some time. Are you just seein

[geos-devel] GEOS 3.7.0 rc1 coming soon

Planning to release GEOS 3.7.0rc1 this weekend or early next. Speak now if you have issues. Only things left are below https://trac.osgeo.org/geos/query?status=assigned=new=reopened =3.7.0 Which I think are issues in older versions, so will push to 3.7.1 if we don't get resolved soon.

Re: [geos-devel] GEOS 3.7.0rc1 release

> From: Greg Troxel [mailto:g...@lexort.com] > I have not tried to test-package geos recently. pkgsrc is at 3.6.2, and this was > my first foray into 3.7 land. > > I see the CAPI change for frechet now. For new .h, I wouldn't have > commented. > But what about Geomet

Re: [geos-devel] GEOS 3.7.0rc1 release

ot;either some arbitrary string or the empty > string", it's just more complicated for no good reason. > > So just drop the ? after the .* [Regina Obe] Come to think of it, I think Sebastian's original didn't have that and I forgot to take it out. Anyway I have ticketed https://trac.osg

Re: [geos-devel] NEWS comments

on the branch used fore 3.7 (which I guess is trunk > after 3.6 branch was made) and then just start editing things in. > [Regina Obe] I'm going to get rid of all of those at 3.7.0 (with just a note that the betas and rcs were released) The reason I put them separate is som

Re: [geos-devel] GEOS 3.7.0rc1 release

apserver-buildkit-2017/geos- > 3.7.0rc1/build/CMakeFiles/CMakeError.log". > > > > -jeff > > [Regina Obe] What's the output of your CMakeError.log say? Thanks, Regina ___ geos-devel mailing list geos-devel@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/geos-devel

Re: [geos-devel] GEOS 3.7.0rc1 release

to > put > it in the release. [Regina Obe] I was thinking about that but in this case I figured people might be using the tar ball for development and if they should make changes and try to send us a patch, I'd want the patch to follow the standard so we should include the .editorco

[geos-devel] GEOS 3.7.0rc1 release

The GEOS development team is pleased to release the 3.7.0beta2 version. https://download.osgeo.org/geos/geos-3.7.0rc1.tar.bz2 Change Log: https://trac.osgeo.org/geos/browser/git/NEWS?rev=3.7.0rc1 Please test and report any issues. NOTE: our git master branch has been flipped to start GEOS 3.8

[geos-devel] configure sed version_release stripper broken under NetBSD - Fix Be more greedy

Did we decide what to do here: https://trac.osgeo.org/geos/ticket/917 Okay to go with Greg's change of being more greedy by dropping the ?. If it fixes NetBSD I'm all for it, as I don't think we'll ever be adding anything after that would be an issue with being more or less greedy Thanks,

Re: [geos-devel] PSC Vote Add Vicky Vergara as GEOS committer

...@lists.osgeo.org] On Behalf Of Dale Lutz Sent: Thursday, July 19, 2018 8:00 PM To: GEOS Development List Subject: Re: [geos-devel] PSC Vote Add Vicky Vergara as GEOS committer +1 On Wed, Jul 18, 2018 at 4:12 PM, Regina Obe < <mailto:l...@pcorp.us> l...@pcorp.us> wrote: > Vicky has

Re: [geos-devel] PSC Vote Add Vicky Vergara as GEOS committer

I like Vicky's interpretation better :) > -Original Message- > From: geos-devel [mailto:geos-devel-boun...@lists.osgeo.org] On Behalf Of > Paul Ramsey > Sent: Monday, July 23, 2018 6:22 PM > To: GEOS Development List > Subject: Re: [geos-devel] PSC Vote Add Vicky Vergara as GEOS

Re: [geos-devel] PSC Vote Add Vicky Vergara as GEOS committer - MOTION PASSED

...@georepublic.de] Sent: Sunday, July 22, 2018 5:13 PM To: Regina Obe Cc: GEOS Development List Subject: Re: [geos-devel] PSC Vote Add Vicky Vergara as GEOS committer Hello all I have read the RFC2 carefully, which still talks about svn but I imagine the same stuff applies to gitea

[geos-devel] PSC Vote Add Vicky Vergara as GEOS committer

Vicky has been doing work modernizing GEOS code to follow newer C++ standards. She plans to do more of this when we flip the switch to GEOS 3.8.0. To make it easier, I'd like to add her as a committer to GEOS project. All PSC folks, please vote and express any concerns. +1 from me Thanks,

Re: [geos-devel] Refactoring CoordinateSequence

Hi Regina, This work would be not cause any changes to the C API, though we would ultimately want to add some functions to the C API to create packed coordinate sequences. Dan On Thu, Aug 30, 2018 at 9:53 AM Regina Obe mailto:l...@pcorp.us> > wrote: I have no objection.

[geos-devel] Planning to release an RC2 later in week or over weekend

If anyone has an issue with me releasing an RC2 release let me know. I'm hoping that will be the last RC we need to release before we do the final 3.7.0 release. Only thing left I want to wrap up before I do is to deal with this one: https://trac.osgeo.org/geos/ticket/894 If I can't find a

Re: [geos-devel] GEOS 3.7.0rc1 release

89 939992.66927296668 > > [1] Abort trap (core dumped) ./XMLTester -v -... > > FAIL testrunner (exit status: 134) > > > > I believe this has normal IEEE754 floating point. > > > > So I'm curious if anyone has run this on arm, and specifically armv7. > &g

Re: [geos-devel] GEOS 3.7.0rc1 release

o the list - obviously I still have things to figure out. [Regina Obe] Greg and Bas, I want to thank you both for all your work testing these platforms. I've been out at conference so been out of it for a bit and just slowly getting back on the horse. I saw you both tested 3.7.0rc2 with ARM and had fail

[geos-devel] TABS or SPACES - ALL DEVELOPERS and PSC Vote

As many know the GEOS code base is a mess of different formatting. Particular with tabs and spaces. Our .editorconfig is equally messy in the name of compromise. I'd like to make a Motion starting with GEOS 3.8 to reformat the .cpp, .h, and .c I think the other extensions are pretty standard and

Re: [geos-devel] TABS or SPACES - ALL DEVELOPERS and PSC Vote

ather than 4 gives more space for code Martin On Mon, Sep 10, 2018 at 9:45 AM Regina Obe mailto:l...@pcorp.us> > wrote: As many know the GEOS code base is a mess of different formatting. Particular with tabs and spaces. Our .editorconfig is equally messy in the name of compr

[geos-devel] GEOS 3.7.0 is released

The GEOS development team is proud to finally release GEOS 3.7.0. After many years of soul searching, we finally got out a release. Note this is the first release to require a C++11 compiler to compile. Source code can be downloaded from: https://download.osgeo.org/geos/geos-3.7.0.tar.bz2 3.7.0

Re: [geos-devel] Refactoring CoordinateSequence

> GEOS' raison d'etre is a native port of JTS, so a "divorce" doesn't seem > fruitful to me. > JTS is recently seeing quite a bit of new development, and it's more > challenging to share improvements if the codebases diverge. > I don't think a line-by-line port is desirable, and we should take

Re: [geos-devel] TABS or SPACES - ALL DEVELOPERS and PSC Vote - MOTION PASSED 4 spaces

Didn't hear any screaming or objections - so proclaiming MOTION PASSED Vicky want to go ahead with your change? Remember one big gorilla commit :) > -Original Message- > From: Regina Obe [mailto:l...@pcorp.us] > Sent: Tuesday, September 11, 2018 1:43 PM > To: 'GEOS Deve

Re: [geos-devel] RFC7 - Use CMake as build system for GEOS

I think there is also the doxygen builds? Which I recall are only in autotools, but I could be mistaken. From: geos-devel [mailto:geos-devel-boun...@lists.osgeo.org] On Behalf Of Paul Ramsey Sent: Friday, October 19, 2018 1:39 PM To: GEOS Development List Subject: Re: [geos-devel] RFC7 -

Re: [geos-devel] CMake Modernization

+1 From: geos-devel [mailto:geos-devel-boun...@lists.osgeo.org] On Behalf Of Paul Ramsey Sent: Friday, October 19, 2018 5:02 PM To: GEOS Development List Subject: [geos-devel] CMake Modernization Since we are going to work on making cmake build a superset of the autotools build (all the

Re: [geos-devel] Branch Hygeine

Wow we had an svn trunk cgal 6 years ago. Yah I would get rid of those, or at least I think I can live with you deleting them. So +1 there. Stable-2.7? You mean stable-3.7. Hmm stable-3.7. I recall Mat tried to do this once, rename the old svn branches removing the svn from them, I

Re: [geos-devel] Branch Hygeine

Sat, Nov 10, 2018 at 03:52:00AM -0500, Regina Obe wrote: > > > Hmm stable-3.7. I recall Mat tried to do this once, rename the old svn > branches removing the svn from them, I forget what happened. I just > remember him reverting right away cause there was something he hadn't

Re: [geos-devel] SharePathsOp

SharePathsOps I think backs this PostGIS function – https://postgis.net/docs/manual-2.5/ST_SharedPaths.html So JTS doesn't have such a thing? Could be a Sandro invention. From: geos-devel [mailto:geos-devel-boun...@lists.osgeo.org] On Behalf Of Martin Davis Sent: Thursday, November

Re: [geos-devel] RFC7 - Use CMake as build system for GEOS

+1. Trying to compile GEOS under autotools hasn't worked for me for some time. I've been using CMake for GEOS exclusively for the past couple of years. From: geos-devel [mailto:geos-devel-boun...@lists.osgeo.org] On Behalf Of Daniel Baston Sent: Monday, October 01, 2018 12:39 PM To: GEOS

Re: [geos-devel] RFC7 - Use CMake as build system for GEOS

their IDE of choice can comfortably run with CMake > > Given two systems (auto* and cmake), and the fact that geos seems to > have had low rate of build system changes, I wonder if there is really > a problem with both. [Regina Obe] The problem with that thinking is that it HA

Re: [geos-devel] RFC7 - Use CMake as build system for GEOS

ly need to support autotools, [Regina Obe] Yes they are required to support multiple build systems without CMake. E.g. Lots of people on windows building with Visual Studio use GEOS which means we need to support NMake if we don't support CMake. Autotools is not supported on native Windows. Cmake ca

Re: [geos-devel] RFC7 - Use CMake as build system for GEOS

hen the change happens [Regina Obe] Alright this is an important point. We can't change to Cmake just yet because autotools is more complete and our model of Cmake use is antiquated and Dan's Cmake changes haven't been fully tested. So first step would be to say – WE OFFICIALLY

[geos-devel] PSC Vote: Drop NMAKE

I think we should drop Nmake. +1 Does anyone have issues with that if we drop in 3.8? I think Cmake is superior in every way for windows building. Thanks, Regna ___ geos-devel mailing list geos-devel@lists.osgeo.org

Re: [geos-devel] RFC7 - Use CMake as build system for GEOS

y default on "systems conforming to POSIX" > rather than just Linux. [Regina Obe] Okay seems pretty clear we can't get rid of autotools, at least not for a while. And as Vicky pointed out the CMake setup in GEOS is kinda old and needs to be reworked of which Dan did a bit of alre

Re: [geos-devel] C++ version, documentation and --std flags

; In my case, I think gcc 4.8 almost entirely supports C++11, but defaults to > C++03 without --std=c++11. > ___ > geos-devel mailing list > geos-devel@lists.osgeo.org > https://lists.osgeo.org/mailman/listinfo/geos-devel [Regina Obe] Wha

Re: [geos-devel] C++ version, documentation and --std flags

X_COMPILE_STDCXX > > > > which is found in configure.ac and defined in > > macros/ax_cxx_compile_stdcxx.m4 > > I do not see that in configure.ac on trunk. But I realize now that's because > I'm > still using the svn repo, and despite the trac showing that under 'browse

Re: [geos-devel] C++ version, documentation and --std flags

> Greg Troxel > Sent: Saturday, October 06, 2018 7:37 PM > To: Sandro Santilli > Cc: GEOS Development List > Subject: Re: [geos-devel] C++ version, documentation and --std flags > > Here's a patch to README.md on git master. It explains the C++11 > requirement, gives clearer examples for using

Re: [geos-devel] Refactoring CoordinateSequence

I have no objection. I know Vicky was complaining about the large number of functions that should be private that are exposed. She was planning to deprecate them in 3.8 and remove/make private in a later release. I'm not sure if this is related to that if she's even looked at that class.

[geos-devel] GEOS 3.7.0rc2 released

/git/NEWS?rev=3.7.0rc2 - Drop ? from extended regular expression, so that the expression strictly conforms to the POSIX ERE rules. (#917, Greg Troxel, Bas Couwenberg) - include .editorconfig in tar ball, fixes Cmake on VS (#920, Jeff Mckenna, Regina

Re: [geos-devel] Deprecation / Removal

As I recall our process is we don't guarantee ABI or API portability of the C++ API we have (at least not on minor versions), micro we try to. That said – if it's not exposed in the C-API, +1 for rip away lah dee dah. Less is more. From: geos-devel

Re: [geos-devel] *.vc files

+1 Wipe out all the VC build files. I think we said in 3.8 we would officially no longer support VS and windows users should use cmake. There are way too many versions of VS to keep track of. Even a windows user is not going to test all permutations and each always seems to require a

Re: [geos-devel] C++14

king it slow is a good idea. > > P > > ___ > geos-devel mailing list > geos-devel@lists.osgeo.org > https://lists.osgeo.org/mailman/listinfo/geos-devel [Regina Obe] +1 for taking it slow. I'm still shipping windows builds with GC

Re: [geos-devel] JTS equalsTopo()

I'm more leaning on the side of "let sleeping dogs lie." Don't we have so many other things where our GEOS is a bit out of synch with JTS. E.g. our weird 3Dish support in GEOS. Is equalsTopo / equals() used in that many places to make not changing it really that difficult to port

Re: [geos-devel] 3.7.1 Release

Which test was that. Might have been the one that was failing on Clang (FreeBSD and Mac) that I shushed in 3.7.0. In which case it's just as well its removed. +1 for release > -Original Message- > From: geos-devel [mailto:geos-devel-boun...@lists.osgeo.org] On Behalf Of > Sandro

Re: [geos-devel] TABS or SPACES - ALL DEVELOPERS and PSC Vote

> > I think that GEOS' style is already quite consistent and doesn't need editor > enforcement and process around it. I mean, we already know it looks, feels, > and acts just like Java :P > > Howard > > [Regina Obe] Well it annoys me and I think others as well. One o

Re: [geos-devel] TABS or SPACES - ALL DEVELOPERS and PSC Vote

Are you in the 2 space camp or the 4 space camp. I prefer tabs, but can live with 4 spaces. 2 spaces will be less bearable. From: geos-devel [mailto:geos-devel-boun...@lists.osgeo.org] On Behalf Of Dale Lutz Sent: Tuesday, September 11, 2018 11:43 AM To: GEOS Development List Subject:

Re: [geos-devel] TABS or SPACES - ALL DEVELOPERS and PSC Vote

> On 9/11/18 6:44 AM, Sandro Santilli wrote: > > On Mon, Sep 10, 2018 at 01:15:25PM -0700, Paul Ramsey wrote: > >> Same. 2-spaces hurts my little brain. > > I'm happy as long as you give me a recipe to make my editor > > (vim) automatically use what we choose AND `make check` ensures any > >

Re: [geos-devel] svn-3.7

It's just called 3.7 now :) - https://git.osgeo.org/gitea/geos/geos/src/branch/3.7 3.7 is the first release not to be on svn. From: geos-devel [mailto:geos-devel-boun...@lists.osgeo.org] On Behalf Of Paul Ramsey Sent: Thursday, September 13, 2018 12:48 PM To: GEOS Development List

Re: [geos-devel] RFC 9: Restore C++ API as public API

-1 Not much has changed since we made this decision to make it non-public. In fact ironically I feel like more people are using GEOS than before. I was hoping removing the C++ public would scare more people away so we could do some major rework :). I'd like us to be able to guarantee some bit

Re: [geos-devel] RFC 9: Restore C++ API as public API

interface for library users. > > And that's the difference in perspective between a developer and distribution > packager. > > Kind Regards, > > Bas > > -- > GPG Key ID: 4096R/6750F10AE88D4AF1 > Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1 [

Re: [geos-devel] RFC 9: Restore C++ API as public API

, C++ APIs are radically better than C for large scale work (aka google) and I really really don't want more custom/external to the package C++ wrappers for C (with or without wrapping C++). http://schwehr.org [Regina Obe] I don't think we should discuss this any further until at least GEOS 3

Re: [geos-devel] RFC 9: Restore C++ API as public API

exity - something GEOS has a an advantage. GEOS should not be used or turned into as Expert only library. Please remember package management is a long standing issue in C/C++ based on its characteristics - those being the same that make them popular when people want primarily performance. On Sat,

Re: [geos-devel] RFC 9: Restore C++ API as public API

_ applications using the C++ API of GEOS. > > Please correct me if I'm wrong > > REF: https://git.osgeo.org/gitea/geos/geos/commit/aae36582e > > --strk; [Regina Obe] I always assumed that's what we were arguing about the actual commit. https://lists.osgeo.org/pipermail/geos-d

  1   2   3   >