Re: 3.13.0beta1 ?

[Jeff McKenna]

On 2024-08-16 8:15 a.m., Mike Taves wrote:

On Fri, 16 Aug 2024 at 14:30, Regina Obe  wrote:


I assume that GEOS there is meant to be GDAL?
What does upgrading CMake buy us.


Oh right, yes GDAL. It mostly buys a fix for MSVC Ninja build
messages, which wasn't fixed to my knowledge.


I'm still hesitant to up the CMake version just for the sake of upping the 
CMake version especially so late in the cycle of GEOS 3.13 development.
If we had done this early own, I would not have an issue.


Understandable, as it is the 11th hour. I have a PR to consider for
GEOS 3.13, otherwise it can wait to be merged for the next dev phase:
https://github.com/libgeos/geos/pull/1143


Thanks Mike.

Regarding trying to get changes made for packagers, as you saw my same 
change rejected here in the previous pull request, I just instead have 
been making that change locally - it avoids the questioning, and helps 
the users downstream, without the firestorm. :)


Enjoy your weekend,

-jeff

Re: 3.13.0beta1 ?

[Jeff McKenna]

Thanks Mike, unfortunately I tried this earlier, unsuccessfully, through 
that pull request that you mentioned (even though it would help 
packagers).  I am not surprised that it came up again.


Thanks for bringing this up again.


-jeff



On 2024-08-15 6:21 p.m., Mike Taves wrote:

I'd like to bump the minimum CMake version to 3.16 for the GEOS 3.13
series. Now is the right time to do this. I don't have a PR ready, but
I can later today.

FWIW, CMake 3.16 is the minimum version for PROJ and GEOS.

See also https://github.com/libgeos/geos/pull/936

On Thu, 15 Aug 2024 at 17:49, Paul Ramsey  wrote:


Any objections to the first beta package? Give packagers a chance to see if the 
new code builds, etc?

P



--
Jeff McKenna
GatewayGeo: Developers of MS4W, & offering MapServer Consulting/Dev
co-founder of FOSS4G
http://gatewaygeo.com/

Re: 3.13.0beta1 ?

[Jeff McKenna]

+1

(will test on Windows/MSVC)

-jeff



On 2024-08-13 9:29 p.m., Paul Ramsey wrote:

Any objections to the first beta package? Give packagers a chance to see if the 
new code builds, etc?

P

'
--
Jeff McKenna
GatewayGeo: Developers of MS4W, & offering MapServer Consulting/Dev
co-founder of FOSS4G
http://gatewaygeo.com/

Re: [geos-devel] cmake => 3.15?

[Jeff McKenna]

Hi all, please disregard the pull request, I have closed it, it is 
easier for me to make the change locally.   This way it doesn't affect 
your builds.


-jeff



On 2023-07-03 7:59 p.m., Regina Obe wrote:
FWIW Debian Buster I think ships with cmake 3.13 and it’s not that old.  
Old but not that old.


-1  to increase the cmake version until the pressing reason can be 
better explained or there are more pressing reasons.


As I recall I think Amazon had to upgrade their CMake to build the 
latest GEOS.


Note Debian Buster ships with 3.13 (which is old but not that old).

I also just approved this run of this pull request, and it broke some of 
our bots like the Ubuntu 20.04, which is kind of in the same boat as 
Debian Buster, old but not that old. Okay maybe in year when it’s time 
to release we can consider it ancient.


What I am curious to understand is why our VS windows 2022 build running 
cmake 3.26.4 
https://github.com/libgeos/geos/actions/runs/5446890161/jobs/9908248625 



Seems to be doing just fine without this patch am I missing something 
here?  What is different about this pull request error.


What version of VS is this using?

Thanks,

Regina

*From:*geos-devel [mailto:geos-devel-boun...@lists.osgeo.org] *On Behalf 
Of *Daniel Baston

*Sent:* Monday, July 3, 2023 5:13 PM
*To:* GEOS Development List 
*Subject:* Re: [geos-devel] cmake => 3.15?

I don't see a problem with requiring 3.15, but the issue isn't very 
clear to me. Is our CMake configuration using some feature of 3.15 while 
declaring that we only require 3.13?


Dan

On Mon, Jul 3, 2023 at 3:56 PM Paul Ramsey > wrote:


For this small fix with MSVC noise...

https://github.com/libgeos/geos/pull/936


It's still quite an old release, my dev env sits at 3.24 for example.

P

___
geos-devel mailing list
geos-devel@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/geos-devel

Re: [geos-devel] Vote on 3.12.0 Release

[Jeff McKenna]

+1

(sorry for my late testing: on Windows with Visual Studio, with beta2, 
all is well, but for the record, during compile of geosop.exe the 
following warnings are thrown, maybe this was reported/handled earlier :



\geos-3.12.0\util\geosop\GeometryOp.cpp(200): warning C4573: the usage 
of 'geos::precision::GeometryPrecisionReducer::reduce' requires the 
compiler to capture 'this' but the current default capture mode does not 
allow it
\geos-3.12.0\util\geosop\GeometryOp.cpp(527): warning C4573: the usage 
of 'geos::operation::distance::DistanceOp::nearestPoints' requires the 
compiler to capture 'this' but the current default capture mode does not 
allow it
\geos-3.12.0\util\geosop\GeometryOp.cpp(528): warning C4573: the usage 
of 'geos::operation::distance::DistanceOp::nearestPoints' requires the 
compiler to capture 'this' but the current default capture mode does not 
allow it
\geos-3.12.0\util\geosop\GeometryOp.cpp(529): warning C4573: the usage 
of 'geos::operation::distance::DistanceOp::nearestPoints' requires the 
compiler to capture 'this' but the current default capture mode does not 
allow it
\geos-3.12.0\util\geosop\GeometryOp.cpp(530): warning C4573: the usage 
of 'geos::operation::distance::DistanceOp::nearestPoints' requires the 
compiler to capture 'this' but the current default capture mode does not 
allow it
\geos-3.12.0\util\geosop\GeometryOp.cpp(538): warning C4573: the usage 
of 'geos::algorithm::distance::DiscreteFrechetDistance::distance' 
requires the compiler to capture 'this' but the current default capture 
mode does not allow it
\geos-3.12.0\util\geosop\GeometryOp.cpp(546): warning C4573: the usage 
of 'geos::algorithm::distance::DiscreteHausdorffDistance::distance' 
requires the compiler to capture 'this' but the current default capture 
mode does not allow it
\geos-3.12.0\util\geosop\GeometryOp.cpp(825): warning C4573: the usage 
of 'geos::operation::intersection::RectangleIntersection::clip' requires 
the compiler to capture 'this' but the current default capture mode does 
not allow it
\geos-3.12.0\util\geosop\GeometryOp.cpp(885): warning C4573: the usage 
of 'geos::coverage::CoverageSimplifier::simplify' requires the compiler 
to capture 'this' but the current default capture mode does not allow it
\geos-3.12.0\util\geosop\GeometryOp.cpp(888): warning C4573: the usage 
of 'geos::coverage::CoverageSimplifier::simplify' requires the compiler 
to capture 'this' but the current default capture mode does not allow it
\geos-3.12.0\util\geosop\GeometryOp.cpp(889): warning C4573: the usage 
of 'geos::coverage::CoverageSimplifier::simplify' requires the compiler 
to capture 'this' but the current default capture mode does not allow it
\geos-3.12.0\util\geosop\GeometryOp.cpp(891): warning C4573: the usage 
of 'geos::coverage::CoverageSimplifier::simplify' requires the compiler 
to capture 'this' but the current default capture mode does not allow it
\geos-3.12.0\util\geosop\GeometryOp.cpp(911): warning C4573: the usage 
of 'geos::coverage::CoverageValidator::validate' requires the compiler 
to capture 'this' but the current default capture mode does not allow it
\geos-3.12.0\util\geosop\GeometryOp.cpp(915): warning C4573: the usage 
of 'geos::coverage::CoverageValidator::validate' requires the compiler 
to capture 'this' but the current default capture mode does not allow it
\geos-3.12.0\util\geosop\GeometryOp.cpp(916): warning C4573: the usage 
of 'geos::coverage::CoverageValidator::validate' requires the compiler 
to capture 'this' but the current default capture mode does not allow it
\geos-3.12.0\util\geosop\GeometryOp.cpp(917): warning C4573: the usage 
of 'geos::coverage::CoverageValidator::validate' requires the compiler 
to capture 'this' but the current default capture mode does not allow it
\geos-3.12.0\util\geosop\GeometryOp.cpp(920): warning C4573: the usage 
of 'geos::coverage::CoverageValidator::validate' requires the compiler 
to capture 'this' but the current default capture mode does not allow it



-jeff




--
Jeff McKenna
GatewayGeo: Developers of MS4W, MapServer Consulting and Training
co-founder of FOSS4G
http://gatewaygeo.com/



On 2023-06-25 8:45 p.m., Paul Ramsey wrote:

Does anyone object to a 3.12.0 release on Monday/Tuesday?

P.



___
geos-devel mailing list
geos-devel@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/geos-devel

Re: [geos-devel] GEOS support for Visual Studio 2015

[Jeff McKenna]

Hi Dan, ok to remove MSVC 2015 (likely the minimum should be MSVC 2019 
today).


thanks,

-jeff



On 2022-11-16 8:18 p.m., Daniel Baston wrote:

Hi,

Not for the first time, I've been testing some code changes that work in 
all of our CI environments except for Visual Studio 2015. We recently 
removed support for gcc 4.8 and I'm wondering if we should consider 
removing support for MSVC 2015 in the same release. Like gcc 4.8, MSVC 
2015 lacks 100% C++11 support. It also requires us to maintain an 
AppVeyor CI setup solely for this compiler. Is there any particular 
interest in this compiler, or can we remove it and save some effort 
implementing workarounds?


Dan


--
Jeff McKenna
GatewayGeo: Developers of MS4W, MapServer Consulting and Training
co-founder of FOSS4G
http://gatewaygeo.com/

___
geos-devel mailing list
geos-devel@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/geos-devel

Re: [geos-devel] GEOS Maintenance Grant

[Jeff McKenna]

Dear GEOS PSC,

Great to hear about a grant to help the project along.

My feedback is to make sure that the funds are spread around, not just 
to one developer, but also to the (even more critical) parts of software 
projects that never receive funding, yet are so important to end-users: 
documentation, testing, and packaging.


I know it is 2022, and we have so many corporate influences in FOSS4G 
that it's hard to see through the activity/smoke, but, we should always 
try to make sure that the funds are spread around to as many parts of 
the project as possible.  For example, 50k USD could be shared by the 
GEOS PSC as:


  - 25k development
  - 10k documentation
  - 10k packaging
  -  5k testing and releases

That is a fair plan for actual project "maintenance". QGIS.ORG (the 
registered entity behind QGIS) & the QGIS PSC does an excellent job at 
spreading the funding around to all parts of the project, which creates 
a "product" feeling to QGIS (a well-rounded result).


My rule of thumb, is that for every 1 hour of development in a software 
project spent, it should take approximately 8 hours of further testing, 
documentation, and packaging by others, if done properly. (instead of 
one funded developer doing an hour of development, and squeezing in a 
few minutes of docs often by the same developer).


I hope my feedback can be received well by the GEOS PSC, and they could 
keep this feedback in mind the next time funding comes along.


Thanks, sent from the east coast of Canada,

-jeff




--
Jeff McKenna
GatewayGeo: Developers of MS4W, MapServer Consulting and Training
co-founder of FOSS4G
http://gatewaygeo.com/



On 2022-02-15 11:37 a.m., Howard Butler wrote:

GDAL PSC,

When we wrote the GDAL RFCs on sponsorship, we provided an escape clause to 
allow us to direct resources to other projects upon which GDAL depends. Our 
sponsorship numbers are still increasing, which provides us an opportunity to 
directly support some of those projects, and one of them is obviously GEOS. 
GEOS provides all of the geometry algebra support for GDAL/OGR and many other 
open source geospatial softwares including Shapely, PostGIS, GeoPandas, 
MapServer, and more.

Dan Baston of the GEOS PSC has been identified as the developer with capacity 
and interest in the next year to take on GEOS development on APIs and 
performance, which he has a long history of doing for the project. This support 
should allow him to work longer, multi-release upgrades that will provide 
strong performance and convenience benefits for the project.

I motion to provide the GEOS PSC with a $50,000 USD grant to address 
performance, API, and other work that does not attract directed funding in 
GEOS. The GEOS PSC will be responsible for coordinating work tasks, rates, and 
development timelines. Howard Butler or Even Rouault of the GDAL NumFocus 
liaison team will coordinate dispersement as directed by the GEOS PSC and 
NumFocus rules.

Thank you again to the GDAL Sponsors https://gdal.org/sponsors/index.html who 
have made this kind of grant possible. A better GEOS makes for a better GDAL.

Howard





___
geos-devel mailing list
geos-devel@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/geos-devel

Re: [geos-devel] 3.10.2 release

[Jeff McKenna]

+1

(I've always called Fridays the "FOSS4G release day")

-jeff



On 2022-01-13 8:54 p.m., Paul Ramsey wrote:

I should roll a new patch release, any objections? Will do it either tomorrow 
or over the weekend.





___
geos-devel mailing list
geos-devel@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/geos-devel

Re: [geos-devel] 3.10.1 Released

[Jeff McKenna]

Ah that was the wrong Action, here is more recent: 
https://github.com/softprops/action-gh-release


(personally I click the button for the release, but others may need 
something more elegant, as above)


-jeff



On 2021-11-15 12:45 p.m., Jeff McKenna wrote:
If you're not into clicking a button, it can also be done auto-magically 
through a GitHub action: https://github.com/actions/create-release


Thanks again!


-jeff



On 2021-11-15 12:34 p.m., Jeff McKenna wrote:

For the release steps, can you also add:

 - generate a release on GitHub (this way all of those 'following' 
this repository are automatically notified of the release)
 - for example, see: 
https://github.com/MapServer/MapServer/releases/tag/rel-7-6-4

 - specifically:
 click the button "Draft a new release" at : 
https://github.com/libgeos/geos/releases


thanks!

-jeff









--
Jeff McKenna
GatewayGeo: Developers of MS4W, MapServer Consulting and Training
co-founder of FOSS4G
http://gatewaygeo.com/
___
geos-devel mailing list
geos-devel@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/geos-devel

Re: [geos-devel] 3.10.1 Released

[Jeff McKenna]

If you're not into clicking a button, it can also be done auto-magically 
through a GitHub action: https://github.com/actions/create-release


Thanks again!


-jeff



On 2021-11-15 12:34 p.m., Jeff McKenna wrote:

For the release steps, can you also add:

     - generate a release on GitHub (this way all of those 'following' 
this repository are automatically notified of the release)
     - for example, see: 
https://github.com/MapServer/MapServer/releases/tag/rel-7-6-4

     - specifically:
     click the button "Draft a new release" at : 
https://github.com/libgeos/geos/releases


thanks!

-jeff






--
Jeff McKenna
GatewayGeo: Developers of MS4W, MapServer Consulting and Training
co-founder of FOSS4G
http://gatewaygeo.com/
___
geos-devel mailing list
geos-devel@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/geos-devel

Re: [geos-devel] 3.10.1 Released

[Jeff McKenna]

For the release steps, can you also add:

- generate a release on GitHub (this way all of those 'following' 
this repository are automatically notified of the release)
- for example, see: 
https://github.com/MapServer/MapServer/releases/tag/rel-7-6-4

- specifically:
click the button "Draft a new release" at : 
https://github.com/libgeos/geos/releases


thanks!

-jeff



--
Jeff McKenna
GatewayGeo: Developers of MS4W, MapServer Consulting and Training
co-founder of FOSS4G
http://gatewaygeo.com/



On 2021-11-02 7:35 p.m., Paul Ramsey wrote:

Due to a mistake on my part in packaging, a second patch release of 3.10 is now 
available. Amazingly there are also already a few little code fixes to bundle 
up with the packaging fix.


https://download.osgeo.org/geos/geos-3.10.1.tar.bz2

Changes in 3.10.1
2021-11-2

- Fixes/Improvements:
   - Fix mistake in constants used to select WKB flavor in C API (GH489, Paul 
Ramsey)
   - Fix crash when reducing precision on a LinearRing (#1135, Paul Ramsey)
   - Fix GeoJSON crash on invalid input (GH498, Even Rouault)
   - Use std::sqrt exclusively for Solaris build (Paul Ramsey)
   - Fix mistaken version numbers in some parts of 3.10.0 (Paul Ramsey)





___
geos-devel mailing list
geos-devel@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/geos-devel

Re: [geos-devel] 3.10.0 Release Vote

[Jeff McKenna]

On 2021-10-18 5:33 p.m., Paul Ramsey wrote:

Having gone through numerous beta and rc releases, and hearing no
further screams of agony, I call the vote on releasing 3.10.0.

+1




+1 jeff



___
geos-devel mailing list
geos-devel@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/geos-devel

Re: [geos-devel] 3.10.0rc2

[Jeff McKenna]

On 2021-10-15 5:53 p.m., Paul Ramsey wrote:

Here it is hopefully ready to go.

https://download.osgeo.org/geos/geos-3.10.0rc2.tar.bz2



Works well here in the MS4W environment!

-jeff




--
Jeff McKenna
GatewayGeo: Developers of MS4W, MapServer Consulting and Training
co-founder of FOSS4G
http://gatewaygeo.com/
___
geos-devel mailing list
geos-devel@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/geos-devel

Re: [geos-devel] 3.10.0rc1 (static)

[Jeff McKenna]

On 2021-10-15 4:33 p.m., Regina Obe wrote:


Paul Ramsey  writes:


OK, this is coming directly out of
https://trac.osgeo.org/geos/ticket/1103

If I go back to using an "OBJECT" library in building ryu, then it
gets bundled right up into libgeos.a where we want it, and your link
line is nice and simple again. That implies a minimum cmake of 3.13,
whcih is 3+ years old now. My macports gives me 3.21 by default. I
dunno, we backed out of the OBJECT library to STATIC to keep the cmake
requirement low, but that implies generating two static libs and
sticking them both on the link line.

I'm inclined to bias towards a newer cmake and still generating one

static

library.

I'm usually in the camp of not wanting to have aggressive dependency
requirements, so having a look and opining.

pkgsrc has 3.21.2 now (and it looks like 3.21.3 just came out).

3.13.0 was released on 2018-11-20.  That's almost 5 years ago, and I

therefore

think it's entirely reasonable to require it if it makes anything even a

little bit

better.

[Regina Obe]
FWIW I'm fine with upping the requirement too.  I'm running with cmake 3.18
at moment but since I just download it from cmake website, I can easily
upgrade too if needed.



I'm fine also with newer cmake requirement (running 3.21.2 here for MS4W 
build environment).


-jeff



--
Jeff McKenna
GatewayGeo: Developers of MS4W, MapServer Consulting and Training
co-founder of FOSS4G
http://gatewaygeo.com/
___
geos-devel mailing list
geos-devel@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/geos-devel

Re: [geos-devel] 3.10.0rc1

[Jeff McKenna]

Building fine on Visual Studio for the MapServer Windows community. 
(the only gotchya was that the RC1 link provided was http which failed 
to download, so https link came to the rescue.


(also, thanks for including .editorconfig in the archive, as if I 
remember correctly I always had to go find that separately, for RC and 
Betas)



-jeff


--
Jeff McKenna
GatewayGeo: Developers of MS4W, MapServer Consulting and Training
co-founder of FOSS4G
http://gatewaygeo.com/



On 2021-10-12 11:02 p.m., Paul Ramsey wrote:

Here it is hopefully ready to go.

http://download.osgeo.org/geos/geos-3.10.0rc1.tar.bz2

P.


___
geos-devel mailing list
geos-devel@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/geos-devel

Re: [geos-devel] RFC7: Discontinue use of autotools

[Jeff McKenna]

On 2021-01-08 6:10 p.m., Sandro Santilli wrote:


As for cross-platform features, that I recall Windows is the only
platform that we've had reports of build problems (for MingW not
being evidently easy to setup - this Regina can say more about).



For MS4W (a huge user-base) I've been using Cmake for GEOS for years in 
the builds for Windows users, without issues.


That said, I maintain Nmake files for many projects (as they moved to 
Cmake and suddenly Windows support breaks), so it's not always easy for 
a project to support Windows, even with Cmake (black-box) magic.


But the magic works for GEOS! ha.

-jeff



--
Jeff McKenna
GatewayGeo: MapServer Consulting and Training Services
co-founder of FOSS4G
http://gatewaygeo.com/
___
geos-devel mailing list
geos-devel@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/geos-devel

Re: [geos-devel] 3.9.0beta2

[Jeff McKenna]

On 2020-12-02 7:17 p.m., Paul Ramsey wrote:

without any further ado, here's a beta2 release for your testing pleasure

http://download.osgeo.org/geos/geos-3.9.0beta2.tar.bz2



+1

tested in the MS4W build environment, on Windows.

-jeff


--
Jeff McKenna
MapServer Consulting and Training Services
co-founder of FOSS4G
http://gatewaygeo.com/






___
geos-devel mailing list
geos-devel@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/geos-devel

Re: [geos-devel] Drop SWIG bindings

[Jeff McKenna]

On 2020-11-25 5:36 p.m., Mike Taves wrote:


Option two: Drop SWIG bindings, including for Ruby and Python
https://github.com/mwtoews/geos/pull/2



+1

(the only one that I've heard interest in is PHP-GEOS, which is already 
hosted/moved elsewhere)


-jeff


--
Jeff McKenna
MapServer Consulting and Training Services
co-founder of FOSS4G
http://gatewaygeo.com/




___
geos-devel mailing list
geos-devel@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/geos-devel

Re: [geos-devel] CMake Modernization

[Jeff McKenna]

+1

-jeff



On 2018-10-19 6:02 PM, Paul Ramsey wrote:
Since we are going to work on making cmake build a superset of the 
autotools build (all the 'convenience' of autotools plus windows and 
other support) I'd like to propose we bring in the large update of cmake 
Mateusz provided recently:


https://github.com/mloskot/geos/tree/ml/modern-cmake

 From there we can add the features we want in autotools on a less 
scrufty baseline. Since we've recently released 3.7 this seems like a 
good time for a larger change.


Any concerns w/ that?

P


___
geos-devel mailing list
geos-devel@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/geos-devel

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

[Jeff McKenna]

On 2018-10-03 4:20 PM, Sandro Santilli wrote:

On Wed, Oct 03, 2018 at 02:14:32PM -0400, Greg Troxel wrote:

Sandro Santilli  writes:

On Mon, Oct 01, 2018 at 12:38:50PM -0400, Daniel Baston wrote:


https://trac.osgeo.org/geos/wiki/RFC7


One of the reasons why I still prefer autotools is its ability
to build tester scripts which work before install (via libtool).
Does cmake allow for that ?


Testing before install, while the previous version (including libraries)
is installed, is to me a requirement for a build system.  Also cross
building.  People keep telling me that cmake does everything auto* does,
but I wonder.

Perhaps we can drop camke and just have autotools, and native windows
(vs mingw/cygwin) users can fund keeping the separate windows makefiles
up to date (yes, that's mostly a joke).


The current situation is really that CMake is a contributed module and
the official build tool _is_ autotools. The problem reported in that
RFC7 is not well-posed in that it assumes contributors are _required_
to support multiple build systems. Truth is they only need to support
autotools, but are convinced CMake is enough because they find the
CMake support in there. If we drop CMake support, they won't bother.

How problematic would that be for contributors ?



Can you define what you mean by "that" in your last sentence?  What are 
you proposing?


-jeff



___
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

[Jeff McKenna]

On 2018-08-23 3:57 PM, Greg Troxel wrote:


Jeff McKenna  writes:


That was it, manually copying the missing file from svn or git, into
the release package (geos-3.7.0rc1.tar.bz2) allows GEOS to compile
with msvc 2017.


It seems better to adjust the cmake stuff not to expect such a file than
to put it in the release.



related ticket: https://trac.osgeo.org/geos/ticket/920


-jeff

___
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

[Jeff McKenna]

That was it, manually copying the missing file from svn or git, into the 
release package (geos-3.7.0rc1.tar.bz2) allows GEOS to compile with msvc 
2017.


-jeff




On 2018-08-23 2:21 PM, Jeff McKenna wrote:

nor does the beta2 package.

I am assuming this file is stored in .git

-jeff



On 2018-08-23 2:20 PM, Jeff McKenna wrote:
Note that the RC1 package does not include a file named 
".editorconfig", not does beta2 release.    -jeff




On 2018-08-23 2:05 PM, Jeff McKenna wrote:
It seems to be a problem in locating the file ".editorconfig" in 
CMakeLists.txt on line #332.   Here is the log file: 
https://pastebin.com/7VBkcpG3


-jeff



On 2018-08-23 1:47 PM, Regina Obe wrote:
-- CMake 3.12.1 successfully configured GEOS using Visual Studio 15 
2017

generator
-- Configuring incomplete, errors occurred!
See also
"D:/build/mapserver-buildkit-2017/geos-
3.7.0rc1/build/CMakeFiles/CMakeOutput.log".
See also
"D:/build/mapserver-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

[Jeff McKenna]

nor does the beta2 package.

I am assuming this file is stored in .git

-jeff



On 2018-08-23 2:20 PM, Jeff McKenna wrote:
Note that the RC1 package does not include a file named ".editorconfig", 
not does beta2 release.    -jeff




On 2018-08-23 2:05 PM, Jeff McKenna wrote:
It seems to be a problem in locating the file ".editorconfig" in 
CMakeLists.txt on line #332.   Here is the log file: 
https://pastebin.com/7VBkcpG3


-jeff



On 2018-08-23 1:47 PM, Regina Obe wrote:
-- CMake 3.12.1 successfully configured GEOS using Visual Studio 15 
2017

generator
-- Configuring incomplete, errors occurred!
See also
"D:/build/mapserver-buildkit-2017/geos-
3.7.0rc1/build/CMakeFiles/CMakeOutput.log".
See also
"D:/build/mapserver-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






--
Jeff McKenna
MapServer Consulting and Training Services
https://gatewaygeomatics.com/
___
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

[Jeff McKenna]

Note that the RC1 package does not include a file named ".editorconfig", 
not does beta2 release.-jeff




On 2018-08-23 2:05 PM, Jeff McKenna wrote:
It seems to be a problem in locating the file ".editorconfig" in 
CMakeLists.txt on line #332.   Here is the log file: 
https://pastebin.com/7VBkcpG3


-jeff



On 2018-08-23 1:47 PM, Regina Obe wrote:

-- CMake 3.12.1 successfully configured GEOS using Visual Studio 15 2017
generator
-- Configuring incomplete, errors occurred!
See also
"D:/build/mapserver-buildkit-2017/geos-
3.7.0rc1/build/CMakeFiles/CMakeOutput.log".
See also
"D:/build/mapserver-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



--
Jeff McKenna
MapServer Consulting and Training Services
https://gatewaygeomatics.com/
___
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

[Jeff McKenna]

It seems to be a problem in locating the file ".editorconfig" in 
CMakeLists.txt on line #332.   Here is the log file: 
https://pastebin.com/7VBkcpG3


-jeff



On 2018-08-23 1:47 PM, Regina Obe wrote:

-- CMake 3.12.1 successfully configured GEOS using Visual Studio 15 2017
generator
-- Configuring incomplete, errors occurred!
See also
"D:/build/mapserver-buildkit-2017/geos-
3.7.0rc1/build/CMakeFiles/CMakeOutput.log".
See also
"D:/build/mapserver-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

[Jeff McKenna]

Testing RC1 with Visual Studio 15.8.1 (2017) on Windows, using cmake, 
returns the following errors (no issues with the 3.6.3 release + cmake):


-- Copying .editorconfig file to 
D:/build/mapserver-buildkit-2017/geos-3.7.0rc1/build

CMake Error at CMakeLists.txt:332 (file):
  file COPY cannot find
  "D:/build/mapserver-buildkit-2017/geos-3.7.0rc1/.editorconfig".


-- Enable GEOS unit tests build - ON
-- Enable GEOS XML tests build - ON
-- Enable GEOS large geometry tests build - ON
-- Enable GEOS performance tests build - ON
-- CMake 3.12.1 successfully configured GEOS using Visual Studio 15 2017 
generator

-- Configuring incomplete, errors occurred!
See also 
"D:/build/mapserver-buildkit-2017/geos-3.7.0rc1/build/CMakeFiles/CMakeOutput.log".
See also 
"D:/build/mapserver-buildkit-2017/geos-3.7.0rc1/build/CMakeFiles/CMakeError.log".




-jeff




___
geos-devel mailing list
geos-devel@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/geos-devel

[geos-devel] Fwd: OSGeo Annual General Meeting - projects please join

[Jeff McKenna]

It would be great to have GEOS make a brief report (2 slides) in Dar for 
the AGM (please signup on the wiki page below).





 Forwarded Message 

Dear OSGeo projects & project officers,

the OSGeo Annual General Meeting (AGM) is scheduled for Thursday morning 
August 30 at 8:00-9:00 in Dar Es Salaam (Tansania).


As Project/Committee officer we ask that you attend, or send a delegate 
from your community. The FOSS4G organizers have given us one hour for 
the meeting, leaving us each with around 2 mins!


This update is about your project and community, rather than about your 
software. We are interested in how your community is doing, the 
opportunities and challenges ahead, and how OSGeo can help.


The shared slide deck is available here (request edit access if required):

* 
https://docs.google.com/presentation/d/1imiG7x09ry7lGvmS15FCVq2Z7yaICY00fcpXBK27TXY/edit?usp=sharing


These slides replace the "Annual General Report" 
(https://github.com/geotools/geotools/wiki/GeoTools-Annual-Report-2017) 
used previously, you may wish to borrow that format for inspiration. You 
still can make an annual report page with extended information if you 
like and link to it.


If you are unable to attend we ask that you submit an annual general 
report to the board email list and attend an IRC board meeting by 
November 2018.


We are coordinating activities on the OSGeo Wiki 
(https://wiki.osgeo.org/wiki/Annual_General_Meeting_2018). Please add 
your project and name to the wiki if you can attend.


Best regards

Astrid Emde (OSGeo Secretary)


___
geos-devel mailing list
geos-devel@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/geos-devel

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

[Jeff McKenna]

On 2018-07-18 8:12 PM, Regina Obe wrote:

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



a vote from a GEOS community member:  +1


jeff




___
geos-devel mailing list
geos-devel@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/geos-devel

[geos-devel] Join the OSGeo Code Sprint Saturday 22 July 2017

[Jeff McKenna]

Hi all,

Please join the OSGeo Code Sprint at FOSS4G Europe on Saturday 22 July 2017!

There’s always plenty to do – it’s not all about programming: 
translation, documentation, packaging, feedback, discussions, 
testing...it's all super important for a project!


If you are interested in participating, please add your project/name in 
this wiki page :


https://wiki.osgeo.org/wiki/FOSS4G-Europe_2017_Code_sprint


If you have questions/comments/ideas please let us know, by contacting 
the Code Sprint Committee at europe-foss4g (at) osgeo (dot) org


The Code Sprint Organizing Team is looking forward to see you!










___
geos-devel mailing list
geos-devel@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/geos-devel

Re: [geos-devel] php-geos 1.0.0 final released

[Jeff McKenna]

Very cool!  Have filed a ticket to remember to include this in the next 
MS4W release (will test your Windows build steps with Visual Studio 
then).  Merry Christmas Sandro.


-jeff



On 2016-12-24 6:04 AM, Sandro Santilli wrote:

The first official release of PHP bindings for GEOS is out.

 https://git.osgeo.org/gogs/geos/php-geos/archive/1.0.0.tar.gz
 ( tag 4b56edb05b, tip commit 6db47f0 )

 https://git.osgeo.org/gogs/geos/php-geos/releases

Merry Christmas !

--strk;



--
Jeff McKenna
MapServer Consulting and Training Services
http://www.gatewaygeomatics.com/




___
geos-devel mailing list
geos-devel@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/geos-devel

Re: [geos-devel] GEOS-3.6.0 released

[Jeff McKenna]

On 2016-10-25 5:00 PM, Even Rouault wrote:

Le mardi 25 octobre 2016 21:43:05, Jeff McKenna a écrit :

On 2016-10-25 4:23 PM, Sebastiaan Couwenberg wrote:

On 10/25/2016 06:07 PM, Sandro Santilli wrote:

  - C++ API changes:
- Automatic memory management for GeometryFactory objects


This change seems to cause the build failures for OSSIM, osmium &

osm2pgsql with GEOS 3.6.0. All three builds fail with these errors:
 'geos::geom::GeometryFactory::GeometryFactory()' is protected within

this context

 'virtual geos::geom::GeometryFactory::~GeometryFactory()' is protected

within this context

What is the proper way to support GeometryFactory for both GEOS 3.5.0
and 3.6.0?


Bas I was also confused (as a packager) seeing these 2 releases come
out, and not sure how all of the many other projects handle the 3.6.0
changes (like GDAL, MapServer, PostGIS etc.).


Haven't tried any of 2 new releases, but GDAL, MapServer and PostGIS use the
GEOS C API, so from the changelogs, shouldn't be affected by the 3.6.0 C++
change.


ok thanks Even.

-jeff




___
geos-devel mailing list
geos-devel@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/geos-devel

Re: [geos-devel] GEOS-3.6.0 released

[Jeff McKenna]

On 2016-10-25 4:47 PM, Sebastiaan Couwenberg wrote:

On 10/25/2016 09:43 PM, Jeff McKenna wrote:

On 2016-10-25 4:23 PM, Sebastiaan Couwenberg wrote:

On 10/25/2016 06:07 PM, Sandro Santilli wrote:

  - C++ API changes:
- Automatic memory management for GeometryFactory objects


This change seems to cause the build failures for OSSIM, osmium &
osm2pgsql with GEOS 3.6.0. All three builds fail with these errors:

 'geos::geom::GeometryFactory::GeometryFactory()' is protected within
this context
 'virtual geos::geom::GeometryFactory::~GeometryFactory()' is protected
within this context

What is the proper way to support GeometryFactory for both GEOS 3.5.0
and 3.6.0?



Bas I was also confused (as a packager) seeing these 2 releases come
out, and not sure how all of the many other projects handle the 3.6.0
changes (like GDAL, MapServer, PostGIS etc.).  So I'm assuming that
packagers like us Bas are to use 3.5.1 for now?


3.5.1 seems to be the safer choice for now, although I haven't tested
the reverse dependencies with that yet (still working through all of
them with 3.6.0).



Ok thanks Bas, that is very helpful.

-jeff



--
Jeff McKenna
MapServer Consulting and Training Services
http://www.gatewaygeomatics.com/






___
geos-devel mailing list
geos-devel@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/geos-devel

Re: [geos-devel] GEOS-3.6.0 released

[Jeff McKenna]

On 2016-10-25 4:23 PM, Sebastiaan Couwenberg wrote:

On 10/25/2016 06:07 PM, Sandro Santilli wrote:

  - C++ API changes:
- Automatic memory management for GeometryFactory objects


This change seems to cause the build failures for OSSIM, osmium &
osm2pgsql with GEOS 3.6.0. All three builds fail with these errors:

 'geos::geom::GeometryFactory::GeometryFactory()' is protected within
this context
 'virtual geos::geom::GeometryFactory::~GeometryFactory()' is protected
within this context

What is the proper way to support GeometryFactory for both GEOS 3.5.0
and 3.6.0?



Bas I was also confused (as a packager) seeing these 2 releases come 
out, and not sure how all of the many other projects handle the 3.6.0 
changes (like GDAL, MapServer, PostGIS etc.).  So I'm assuming that 
packagers like us Bas are to use 3.5.1 for now?


-jeff



--
Jeff McKenna
MapServer Consulting and Training Services
http://www.gatewaygeomatics.com/





___
geos-devel mailing list
geos-devel@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/geos-devel

[geos-devel] patch for latest Visual Studio compiler (2015)

[Jeff McKenna]

I've filed a patch to handle nmake builds with the latest MSVC compiler 
(2015 update 1) at https://trac.osgeo.org/geos/ticket/775


-jeff


--
Jeff McKenna
MapServer Consulting and Training Services
http://www.gatewaygeomatics.com/





___
geos-devel mailing list
geos-devel@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/geos-devel

Re: [geos-devel] Build errors in StringTokenizer.cpp with 3.5.0/trunk/branch-3.5

[Jeff McKenna]

On 2016-01-27 2:34 PM, Even Rouault wrote:



C89 and .cpp file, no ;-) I'd rather bet that #include  would fix that


Thanks, you are right of course.  Thanks (humbled again, ha!).  I've 
filed the little patch.  https://trac.osgeo.org/geos/ticket/766


-jeff




--
Jeff McKenna
MapServer Consulting and Training Services
http://www.gatewaygeomatics.com/


___
geos-devel mailing list
geos-devel@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/geos-devel

[geos-devel] Build errors in StringTokenizer.cpp with 3.5.0/trunk/branch-3.5

[Jeff McKenna]

Hello everyone,

Compiling on Windows with Visual Studio 2008 I get the same errors with 
the 3.5.0 release, SVN trunk, and branch 3.5, but I can't find any 
mention of this problem in Trac or on this list.  Here is the error:



StringTokenizer.cpp
io\StringTokenizer.cpp(60) : error C2039: 'numeric_limits' : is not a 
member of 'std'
io\StringTokenizer.cpp(60) : error C2065: 'numeric_limits' : undeclared 
identifier

io\StringTokenizer.cpp(60) : error C2062: type 'double' unexpected
io\StringTokenizer.cpp(60) : error C2039: 'infinity' : is not a member 
of '`global namespa

ce''
io\StringTokenizer.cpp(62) : error C2039: 'numeric_limits' : is not a 
member of 'std'
io\StringTokenizer.cpp(62) : error C2065: 'numeric_limits' : undeclared 
identifier

io\StringTokenizer.cpp(62) : error C2062: type 'double' unexpected
io\StringTokenizer.cpp(62) : error C2039: 'infinity' : is not a member 
of '`global namespa

ce''
io\StringTokenizer.cpp(67) : error C2039: 'numeric_limits' : is not a 
member of 'std'
io\StringTokenizer.cpp(67) : error C2065: 'numeric_limits' : undeclared 
identifier

io\StringTokenizer.cpp(67) : error C2062: type 'double' unexpected
io\StringTokenizer.cpp(67) : error C2039: 'quiet_NaN' : is not a member 
of '`global namesp

ace''
NMAKE : fatal error U1077: '"C:\Program Files\Microsoft Visual Studio 
9.0\VC\BIN\cl.EXE"'

: return code '0x2'
Stop.
NMAKE : fatal error U1077: '"C:\Program Files\Microsoft Visual Studio 
9.0\VC\BIN\nmake.EXE

"' : return code '0x2'
Stop.


If I had to guess, I would guess that these are C89 issues (not 
declaring variables at beginning of the block).


-jeff



--
Jeff McKenna
MapServer Consulting and Training Services
http://www.gatewaygeomatics.com/




___
geos-devel mailing list
geos-devel@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/geos-devel

Re: [geos-devel] branch vs trunk

[Jeff McKenna]

Ok, thanks.  I'll watch for around September.

I can imagine today's GDAL 2.0 release will cause more people than me 
banging on the door though :)


-jeff



On 2015-06-18 8:03 PM, Paragon Corporation wrote:

Yes we are shooting to get GEOS 3.5.0 out the door before PostGIS 2.2. So
probably before September.  A few important  PostGIS 2.2 functions rely on
GEOS 3.5 functionality.

Strk,

Any comments?

Thanks,
Regina

-Original Message-
From: geos-devel-boun...@lists.osgeo.org
[mailto:geos-devel-boun...@lists.osgeo.org] On Behalf Of Greg Troxel
Sent: Thursday, June 18, 2015 5:39 PM
To: Jeff McKenna
Cc: geos-devel@lists.osgeo.org
Subject: Re: [geos-devel] branch vs trunk


Jeff McKenna  writes:


On second thought, I decided to go with the stable branch (/3.4).

Sorry for the noise.


It was actually a really good question.   My opinion (I maintain the
pkgsrc entry) is that you should only package releases, which sounds like
your standard practice too.  But 3.5-to-be is starting to get used as an
almost-dependency by postgis, and I expect pressure from that to
lead to a 3.5 release within the next half year.   (I'm not involved;
that's just a guess as a packager/lurker.)


___
geos-devel mailing list
geos-devel@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/geos-devel

Re: [geos-devel] branch vs trunk

[Jeff McKenna]

Hi Greg, thanks, yes I agree, I will use the 3.4 branch until such 
external pressure (more pressure than little 'ol me) comes from beyond. 
 -jeff




On 2015-06-18 6:39 PM, Greg Troxel wrote:


Jeff McKenna  writes:


On second thought, I decided to go with the stable branch (/3.4).

Sorry for the noise.


It was actually a really good question.   My opinion (I maintain the
pkgsrc entry) is that you should only package releases, which sounds
like your standard practice too.  But 3.5-to-be is starting to get used
as an almost-dependency by postgis, and I expect pressure from that to
lead to a 3.5 release within the next half year.   (I'm not involved;
that's just a guess as a packager/lurker.)



___
geos-devel mailing list
geos-devel@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/geos-devel

Re: [geos-devel] branch vs trunk

[Jeff McKenna]

On second thought, I decided to go with the stable branch (/3.4).

Sorry for the noise.

-jeff




On 2015-06-18 5:15 PM, Jeff McKenna wrote:

Hi all,

As a package maintainer, should I be using GEOS from trunk, or through
branch 3.4?  I notice that there hasn't been a release in almost 2
years, so, I want to make sure that I use an updated version.  I see
some changes done recently in trunk, so I will head down that path,
compiling, for now...

-jeff




___
geos-devel mailing list
geos-devel@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/geos-devel

[geos-devel] branch vs trunk

[Jeff McKenna]

Hi all,

As a package maintainer, should I be using GEOS from trunk, or through 
branch 3.4?  I notice that there hasn't been a release in almost 2 
years, so, I want to make sure that I use an updated version.  I see 
some changes done recently in trunk, so I will head down that path, 
compiling, for now...


-jeff



--
Jeff McKenna
MapServer Consulting and Training Services
http://www.gatewaygeomatics.com/



___
geos-devel mailing list
geos-devel@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/geos-devel

Re: [geos-devel] Compiling GEOS 64-bit

[Jeff McKenna]

On 2013-04-05 11:54 AM, Crispin Cooper wrote:
> Hi, quick question:
> 
> Is there an option I can feed to nmake (building under windows/msvc)
> that will cause GEOS to be compiled 64-bit?
> 
> Best regards
> 
> Crispin
> 
> 

Hi,

I've compiled GEOS in 64-bit on windows/msvc and I did not need any
special option.

-jeff



-- 
Jeff McKenna
MapServer Consulting and Training Services
http://www.gatewaygeomatics.com/


___
geos-devel mailing list
geos-devel@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/geos-devel

Re: [geos-devel] newbie user and visual studio

[Jeff McKenna]

On 12-06-21 12:13 PM, Lloyd Dupont wrote:
> HI,
>  
> I’m a Windows developer (and visual studio user) who is not very good
> with all those open source command line tools.
> I’m also quite rusty with C++ but I want to give it a new go and port
> one of my C# app to C++ (WinRT / Metro C++ Cx to be exact)
>  
> For that I will need some geometry manipulating library, GEOS seems
> liked a good and simple enough candidate.
>  
> To facilitate this difficult entry in the C++ world (with a big open
> source library) it would be nice if there is a way to get a Visual
> Studio project to open which contains all the necessary GEOS file.
>  
> I even found a link which seems to indicate it does exists:
> http://trac.osgeo.org/geos/wiki/BuildingOnWindowsWithVisualStudioIDE
>  
> But I couldn’t find this VS project file.. they seem to be part of the
> build output.. :~
> How to I generate get them??!?
>  
> Thanks for nay links / info / feedback!

Hello,

You can use the Visual Studio Command Prompt to compile GEOS (look for
the shortcut in your Start Menu).  Then a few commands will do the trick:

  autogen.bat
  nmake /f makefile.vc MSVC_VER=1500

(if you are using MSVC 2008)

I am not aware of a Visual Studio solution file that you ask for.

Have fun!

-jeff


-- 
Jeff McKenna
MapServer Consulting and Training Services
http://www.gatewaygeomatics.com/




___
geos-devel mailing list
geos-devel@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/geos-devel

Re: [geos-devel] 3.3.3?

[Jeff McKenna]

None here, I think I put out a release with geos-trunk to get those 
fixes.  Sooner the better :)


-jeff

--
Jeff McKenna
MapServer Consulting and Training Services
http://www.gatewaygeomatics.com/


___
geos-devel mailing list
geos-devel@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/geos-devel

Re: [geos-devel] Call for test of the 3.3 branch

[Jeff McKenna]

On 12-01-06 5:36 PM, Howard Butler wrote:

Fixed in 3.3 branch http://trac.osgeo.org/geos/ticket/506  Please test.



Thanks, it builds fine now on Windows.

-jeff



--
Jeff McKenna
MapServer Consulting and Training Services
http://www.gatewaygeomatics.com/


___
geos-devel mailing list
geos-devel@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/geos-devel

Re: [geos-devel] Call for test of the 3.3 branch

[Jeff McKenna]

I'm trying to compile 3.3.2 on Windows (MSVC 2008/9.0) and getting the 
following error:


{{{
BufferOp.cpp
operation\buffer\BufferOp.cpp(97) : error C2668: 'log' : ambiguous call 
to overloaded fun

tion
C:\Program Files\Microsoft Visual Studio 
9.0\VC\INCLUDE\math.h(121): could be 'do

ble log(double)'
C:\Program Files\Microsoft Visual Studio 
9.0\VC\INCLUDE\math.h(519): or   'fl

at log(float)'
C:\Program Files\Microsoft Visual Studio 
9.0\VC\INCLUDE\math.h(567): or   'lo

g double log(long double)'
while trying to match the argument list '(int)'
NMAKE : fatal error U1077: '"C:\Program Files\Microsoft Visual Studio 
9.0\VC\BIN\cl.EXE"'

: return code '0x2'
Stop.
NMAKE : fatal error U1077: '"C:\Program Files\Microsoft Visual Studio 
9.0\VC\BIN\nmake.EX

"' : return code '0x2'
Stop.
}}}

Anyone have any ideas?

-jeff




On 11-12-09 6:59 AM, Sandro Santilli wrote:

I've spent the last couple of weeks hunting buffer robustness
issues and fixing few more bugs in the 3.3 branch.

I'd release a 3.3.2 shortly with the fixes.

Biggest change is in Buffer operation, specifically in handling
of reduced precision buffering in case of a topology exception
raised with the full-precision attempt.

As I also applied a few patch supposedly fixing build on different
architectures I'd like to call for tests of the branch prior to
closing up the release.

Here's a list of bugfixes:
http://trac.osgeo.org/geos/query?status=closed&order=priority&col=id&col=summary&col=status&col=type&col=priority&col=milestone&col=component&milestone=3.3.2

Still open issues (not sure they'll make it into 3.3.2):
http://trac.osgeo.org/geos/query?status=assigned&status=new&status=reopened&order=priority&col=id&col=summary&col=milestone&col=status&col=type&col=priority&col=component&milestone=3.3.2

Thanks for testing.



--
Jeff McKenna
MapServer Consulting and Training Services
http://www.gatewaygeomatics.com/


___
geos-devel mailing list
geos-devel@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/geos-devel

Re: [geos-devel] Building on Windows

[Jeff McKenna]

Alex Trofast wrote:

Greetings GEOS developers,

I have the pleasure of porting Ingres Geospatial to Windows and hence I 
now must also compile GEOS. I have VS2008 and I used the solution files 
in build/msvc90/ and they built fine for me, putting the .lib and .dll 
files in the Release directory. What I'm wondering is, does GEOS use a 
certain structure when installing on Windows such as:

geos
geos\bin\geos_c.dll
geos\bin\geos_c_i.lib
geos\inc\geos_c.h
geos\inc\geos\version.h

And so on... Or is this up to whoever uses it/software project that uses 
it? Is there already a sort of packager, installer in GEOS on Windows?

Any help is greatly appreciated

Thank you,


Hi Alex,

I'm not a GEOS developer, I'm a packager like yourself (I package GEOS 
for use with MapServer for Windows)...and I see that nobody responded to 
you.  Well I'm in the same situation as you, so, feel comforted now :)


For the record, I also use VS2008, and I compile through the VS2008 
command prompt.


I don't think there is a standard for installing this package on Windows 
- basically it's up to you to decide that.


So, I don't have much info for you, other than yes there are a few of us 
Windows packagers lurking around! :)


-jeff



--
Jeff McKenna
MapServer Consulting and Training Services
http://www.gatewaygeomatics.com/


___
geos-devel mailing list
geos-devel@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/geos-devel

Re: [geos-devel] how to compile this new package

[Jeff McKenna]

南野秀一 南野秀一 wrote:
> Please take a look at the following page.
>  
> http://trac.osgeo.org/geos/ticket/274
>  
> I can't build geos-3.1.1. Please tell me what is wrong and how to fix it 
> step by step. Thanks.
>  
>  

When you install MSVC 2005 or 2008, there should be some shortcuts in
your start menu: use the "Visual Studio 2005/2008 Command Prompt" one.
Then you can cd into the /geos directory and execute the commands:

  autogen.bat
  nmake /f makefile.vc MSVC_VER=1500 (for msvc 2008)

-jeff


-- 
Jeff McKenna
FOSS4G Consulting and Training Services
http://www.gatewaygeomatics.com/


___
geos-devel mailing list
geos-devel@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/geos-devel