From: Nala Ginrut <nalaginrut@gmail.com>
To: "Aleix Conchillo Flaqué" <aconchillo@gmail.com>
Cc: guile-devel <guile-devel@gnu.org>
Subject: Re: ffi for glutInit
Date: Thu, 26 Jul 2012 10:30:59 +0800 [thread overview]
Message-ID: <CAPjoZoeGp36trETS58GkbU56+FQEVrCr3_Kbqq-kzuWFg9Z0HQ@mail.gmail.com> (raw)
In-Reply-To: <CA+XASoV+uQguXKDsoceYb_OJvOHgaBrA7F+TXqcrtwc9Jsd-xw@mail.gmail.com>
hi Aleix!
For our FFI system:
char** <==> '* <==> (quote *)
I'm not sure I understand your question correctly.
I assume that you want to know what's the presentation of char** for
dynamic-func.
On Thu, Jul 26, 2012 at 6:19 AM, Aleix Conchillo Flaqué
<aconchillo@gmail.com> wrote:
> Hi,
>
> I have started working on bindings for OpenGL and GLUT.
>
> https://github.com/aconchillo/guile-gl
>
> The work is very preliminar, which means I can't even show a window yet.
>
> The scm files are semi-automatically generated by a python script that
> uses pycparser. So that saved quite a lot of time.
>
> Now, I'm stuck with glutInit. The signature of the function is like this:
>
> glutInit(int *argc, char **argv);
>
> See: http://www.opengl.org/resources/libraries/glut/spec3/node10.html
>
> I don't really know how to do the char** part, so I need some help here.
>
> For the user, the guile procedure will simply look like (glutInit) and
> internally (command-line) would be ideally used to construct the
> char**, etc.
>
> All other functions in glut.scm should work (at least they evaluate
> fine), except the ones related to fonts. So I would say that glutInit
> is the last one to have a basic program that runs OpenGL.
>
> Thanks in advance,
>
> Aleix
>
next prev parent reply other threads:[~2012-07-26 2:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-25 22:19 ffi for glutInit Aleix Conchillo Flaqué
2012-07-26 2:30 ` Nala Ginrut [this message]
2012-07-26 15:46 ` Aleix Conchillo Flaqué
2012-07-26 16:33 ` Mark H Weaver
2012-07-26 16:39 ` Mark H Weaver
2012-07-26 18:07 ` Nala Ginrut
2012-08-04 16:19 ` Aleix Conchillo Flaqué
2013-01-21 12:04 ` Andy Wingo
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=CAPjoZoeGp36trETS58GkbU56+FQEVrCr3_Kbqq-kzuWFg9Z0HQ@mail.gmail.com \
--to=nalaginrut@gmail.com \
--cc=aconchillo@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).