On Mar 30, 2009, at 7:27 PM, William Kyngesburye wrote:

Finally got some time to actually try it. Error in python vdigit - it's looking for geos_c.h, from Vect.h.

For the linking, it works on OSX as is, but only because I include both C++ and C APIs (libgeos and libgeos_c) in the same binary in the GEOS framework. On other platforms, libgeos_c is probably necessary.

On Mar 30, 2009, at 5:24 PM, William Kyngesburye wrote:

On Mar 30, 2009, at 4:57 PM, Martin Landa wrote:

Is GEOS support really using the C++ API? geos-config --libs only returns
the C++ linking info.

No, C API.

Then add -lgeos_c the GEOS_LIBS? Though you might want an extra check to verify libgeos_c exists.

Maybe this is where Michael is having problems.

Searching the rest of the source, I don't see GEOS used, yet, so there should be no problems compiling --without-geos. Is this yet to come?

lib/vector/Vlib/geos.c
vector/v.select/geos.c

Strange, my text search for GEOSLIBS and GEOSCLFAGS didn't turn up anything (except in configure where I looked with my eyes), yet I see them in platform.make.in, grass.make and vlib/makefile. Must have had a filter on.

-----
William Kyngesb


So you're saying that vdigit doesn't work again because of the geos problem?

Michael
_______________________________________________
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Reply via email to