unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: David Pirotte <david@altosw.be>
To: Amirouche Boubekki <amirouche.boubekki@gmail.com>
Cc: guile-devel <guile-devel@gnu.org>
Subject: Re: clutter, clutter-glx [1.12.2] generating doc, 2 errors
Date: Sun, 13 Apr 2014 15:22:13 -0300	[thread overview]
Message-ID: <20140413152213.404f8a15@capac> (raw)
In-Reply-To: <CAL7_Mo_EUnab3Gu5LXXEh9v10FbdF9ALO5D2jRMfAAoeGn99Vw@mail.gmail.com>

Folks,

> > On Sat, 12 Apr 2014 23:28:18 -0300
> > David Pirotte <david@altosw.be> wrote:
> > > Hello,
> > >
> > >       I'm on guile (GNU Guile) 2.0.11.2-0ece4 now
> > >
> > > Although I did not update the wrapset.api yet, in order to get a
> > > general picture of updating a clutter  binding
> >
> > Provide a binding for clutter's gobject-introspection interface and you
> > will carry most other gobject based libraries with you.
> >
> 
> True. There is already [1] that is meant to do it, I don't know if it still
> works.
> 
> I imagine it would be a significant amount of work though.
> >
> 
> I'm not sure about that. There are several such "bindings" in Python using
> different approach (pure/non-pure, ctypes, cffi, cython,...) and targeting
> different VMs (PyPy, CPython 3.x). Even if it's not easy there is a lot of
> code to learn how to do it.

Please don't answer bug related emails, about existing, perfectly working and
supported modules, as if the original email was an invitation for a talk about what
we should do or what should have been done...

Thanks,
David



      reply	other threads:[~2014-04-13 18:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-13  2:28 clutter, clutter-glx [1.12.2] generating doc, 2 errors David Pirotte
2014-04-13 12:58 ` Chris Vine
2014-04-13 16:56   ` Amirouche Boubekki
2014-04-13 18:22     ` David Pirotte [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20140413152213.404f8a15@capac \
    --to=david@altosw.be \
    --cc=amirouche.boubekki@gmail.com \
    --cc=guile-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).