[gdal-dev] Ruby bindings

Even Rouault even.rouault at spatialys.com
Wed Mar 18 21:03:14 PDT 2015


Selon Ari Jolma <ari.jolma at gmail.com>:

> 19.03.2015, 05:55, Even Rouault kirjoitti:
> > Hi,
> >
> > The build of Ruby bindings is broken in trunk. See
> > http://trac.osgeo.org/gdal/ticket/5880
> >
> > The situation is that, in years, nobody has really maintained them, so it
> isn't
> > even sure that they work at runtime once compilation issues are fixed. So
> we
> > might just have to wipe them out, or remove them from configure, if nobody
> steps
> > up to maintain them. Opinions ?
>
> IMO, remove from configure. Or, at least make it non-automatic.

It is non automatic at the moment, but it doesn't make sense to provide an
option that when enabled cause a build failure.

>
> I would have thought the cause was me since I did some changes in the
> common include files but that does not seem to be the case. For some
> reason ogr_error_map.i is not included when making gdal_wrap.cpp. It
> should be since it is in the ruby typemaps??

$ grep -r ogr_error_map swig/include/
swig/include/ogr_error_map.i: * $Id: ogr_error_map.i 12444 2007-10-16 17:48:23Z
ajolma $
swig/include/perl/typemaps_perl.i:%import "ogr_error_map.i"
swig/include/ruby/typemaps_ruby.i:%include ogr_error_map.i
swig/include/java/typemaps_java.i:%import "ogr_error_map.i"
swig/include/python/typemaps_python.i:%import "ogr_error_map.i"

So the difference is that the ruby bindings do a include and not a import. The
difference between the two always goes above my head without looking at swig
docs. Anyway the problem is that there's no core maintainer with interest in
ruby bindings.

>
> Ari
>
> >
> > Even
> >
>
> _______________________________________________
> gdal-dev mailing list
> gdal-dev at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/gdal-dev
>


-- 
Spatialys - Geospatial professional services
http://www.spatialys.com


More information about the gdal-dev mailing list