[Gegl-developer] Python bindings.

[Øyvind Kolås]

On 8/21/06, Victor Bogado da Silva Lins <bogado at bogado.net> wrote:
> I am trying, as in not being very successfully, to make a python biding
> for gegl. I had hit a first road block. When I call gegl_init from my
> binding it gives me a segmentation fault.
>
> The problem seems to be in the babl library, it has a 'db' global that
> is being used uninitialized. I particularly think that such globals
> should be a class variable, gobject do suport them or am I mistaken?

Babl doesn't use GObject (or even glib), but it's a simple type model
for color models, data types, conversions, samples etc. Each type has
a compilation unit static database, all of them called db, since that
is how it gets defined in babl-internal.h. Thus it cannot be linked
wrong, and not using the name "db" for a non exported symbol seems
quite strict to me.

Does GEGL seem to work (the gegl binary), when not trying to make a
python extension?

/Øyvind K.
-- 
«The future is already here. It's just not very evenly distributed»
                                                 -- William Gibson
http://pippin.gimp.org/                            http://ffii.org/