unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: "Bill Schottstaedt" <bil@ccrma.Stanford.EDU>
To: "Maciek Godek" <pstrychuj@gmail.com>, guile-user@gnu.org
Subject: Re: What new libraries or functionality does Guile need?
Date: Sat, 19 Jul 2008 11:10:12 -0700	[thread overview]
Message-ID: <20080719180348.M46975@ccrma.Stanford.EDU> (raw)
In-Reply-To: <e2ceda030807182249h572cd05fi1fa22beebb5b2eff@mail.gmail.com>

> that it could be wiser to write a semi 
> automatic tool for making guile bindings from C headers

For gl.c in the snd (or libxm) tarball, that's tools/makegl.scm,
using the predigested header info in gldata.scm.  gl.c needs
only xen.[ch], I think, so you could easily extract it from Snd.
There's a similar (but much fancier) script for the Glib/Gdk/Gtk
bindings in xg.c: makexg.scm which uses xgdata.scm. 
snd-gl.scm has a few examples of using openGL in Guile.
I just remembered, you'll also need mus-config.h.






  reply	other threads:[~2008-07-19 18:10 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-18 17:13 What new libraries or functionality does Guile need? Mike Gran
2008-07-18 17:39 ` Julian Graham
2008-07-18 18:32 ` Andre Kuehne
2008-07-19  0:40 ` Jose A. Ortega Ruiz
2008-07-19  5:49   ` Maciek Godek
2008-07-19 18:10     ` Bill Schottstaedt [this message]
2008-07-20 20:42 ` Ludovic Courtès
2008-07-20 22:35   ` Mike Gran
2008-07-21  6:34 ` Thien-Thi Nguyen
  -- strict thread matches above, loose matches on Subject: below --
2008-07-18 18:38 Mike Gran
2008-07-18 19:37 dsmich
2008-07-18 19:43 dsmich
     [not found] <cmu-lmtpd-23333-1216458306-3@mail-imap1.uio.no>
2008-07-19 11:08 ` Kjetil S. Matheussen
2008-07-21 16:02   ` JonWilson
2008-07-22 13:09     ` Bill Schottstaedt
     [not found] <cmu-lmtpd-5742-1216742728-1@mail-imap1.uio.no>
2008-07-22 16:24 ` Kjetil S. Matheussen

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=20080719180348.M46975@ccrma.Stanford.EDU \
    --to=bil@ccrma.stanford.edu \
    --cc=guile-user@gnu.org \
    --cc=pstrychuj@gmail.com \
    /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).