SWIG bindings segmentation fault

[cfis@…]

The Geos 2.2.1 SWIG bindings don't deal with memory management very well. If you try to run the equivalent of example.cpp in Python you will get segmentation faults. I've sent a patch to the geos mailing list that solve the problem.

[cfis@…]

SWIG patch for 2.2.2

[cfis@…]

New Ruby bindings

[cfis@…]

Python Swig file

[cfis@…]

Patches:
 
cfis_swig.patch - Apply normally
ruby.zip - unzip under geos/swig
python.i - put in geos/swig/python

What these files do:

* Updates memory handling, you can now run the equivalent of example.cpp
in python / ruby without causing segmentation faults

* Updates methods like WKBReader.read so that they return the
appropriate geometry type (point, line, etc.) as opposed to
Geos::Geometry.

* Limits the exposed api.  Only exposes geom.h, version.h, util.h, io.h

* Exposes WKBReader.read/write and WKTReader.read/write and WKBWriter.read/write and WKTWriter.read/write which were not previously available from scripting languages

* Adds Ruby support, with test cases

[strk@…]

Applied to the 2.2 branch, with Makefile.am
modified to not attempt automatic build.

[(none)]

Milestone 2.2.2 deleted