update geos to 3.3.6

[aperi2007]

Hi,

The osgeo4w host the geos 3.3.5

The last released version is geos 3.3.6.

I guess it should surely better because it resolve a single bug on intersection. See the image:

I'm not sure if this can help. However I put the package geos 3.3.6 compiled from sources using VisualC 2008 32 bit on windows platform.

[aperi2007]

I was unable to put the package compiled on this ticket (too large size). However if this package can help please say me how I can post it.

Regards,

Andrea.

[jef]

I wonder what the upload limit is - the latest geos package in osgeo4w is just ~500k. Do you have the package somewhere else for review?

[aperi2007]

I guess the oversize is the static library (libgeos.lib) that has about 56 MB. Perhaps the package of osgeo4w use only the shared ?

[aperi2007]

I try to repackage removing the static lib and the size now is about 950 KB.

[jef]

Replying to aperi2007:

I guess the oversize is the static library (libgeos.lib) that has about 56 MB. Perhaps the package of osgeo4w use only the shared ?

Please review the old ​http://download.osgeo.org/osgeo4w/release/geos/geos-3.3.5-1.tar.bz2 package - a new package should have the same structure.

[aperi2007]

I produce a package more like to the 3.3.5 old package. But there are still some difference.

VC2008 don't produce the geos_c_i.lib it produced the geos_c.lib. I guess is more correct the geos_c.lib with the geos_c.dll

Also I see a really little bug in the source of the released 3.3.6 It in the version.h file has the version numbered as "3.3.6dev" instead of "3.3.6".

[aperi2007]

Hi,

The package compiled for geos 3.3.6 is downloadable from this link.

​http://tinyurl.com/c5gt6m9

Regard,

[jef]

Replying to aperi2007:

Hi,

The package compiled for geos 3.3.6 is downloadable from this link.

​http://tinyurl.com/c5gt6m9

Um, that's a zip file. Anyway, I've uploaded a 3.3.6 package.

[brushtyler]

Replying to aperi2007:

VC2008 don't produce the geos_c_i.lib it produced the geos_c.lib. I guess is more correct the geos_c.lib with the geos_c.dll

IIRC Frank asked me to remove the static libraries from my packages and keep the import libraries "_i.lib" when I built the freexl/sqlite/spatialite libs (I'm searching for that discussion but I'm unable to find it, probably it was on IRC).

[aperi2007]

IIRC Frank asked me to remove the static libraries from my packages and keep the import libraries "_i.lib" when I built the freexl/sqlite/spatialite libs (I'm searching for that discussion but I'm unable to find it, probably it was on IRC).

I guess in a system like osgeo4w born to allow the use of various gis systems the static library is really unuseful. The shared lib are the more appropriately. If there are more systems that need differents versions of a lib i guess is better to maintain in the package also the previous versions of that lib. Instead if the osgeo4w is see also as a container of all the libs need to a GIS developer to support him, the static libs could have a role. However I still think that in a develop environment a developer should still use the shared libs.

my 2ct.