From: Erik de Castro Lopo <mle+ocaml@mega-nerd.com>
To: caml-list@inria.fr
Subject: Creating wrappers for C libraries
Date: Fri, 8 Dec 2006 15:54:37 +1100 [thread overview]
Message-ID: <20061208155437.7ed85c4f.mle+ocaml@mega-nerd.com> (raw)
Hi all,
I've had a look at chapter 12 of the O'Rielly book as well as the
wrapper for ocaml-fftw3 and cairo-ocaml and it all seems a little
daunting.
I was wondering if there was any semi-automated too for creating
Ocaml bindings for C libraries.
Any pointers appreciated.
Cheers,
Erik
--
+-----------------------------------------------------------+
Erik de Castro Lopo
+-----------------------------------------------------------+
"Lumping configuration data, security data, kernel tuning parameters,
etc. into one monstrous fragile binary data structure is really dumb."
- David F. Skoll
next reply other threads:[~2006-12-08 4:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-08 4:54 Erik de Castro Lopo [this message]
2006-12-08 6:36 ` [Caml-list] " Chris King
2006-12-08 6:45 ` Sébastien Hinderer
2006-12-08 7:08 ` [Caml-list] " Jon Harrop
2006-12-08 10:18 ` David Baelde
2006-12-08 11:08 ` Sébastien Hinderer
2006-12-08 11:41 ` [Caml-list] " Richard Jones
2006-12-08 12:00 ` Daniel Bünzli
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20061208155437.7ed85c4f.mle+ocaml@mega-nerd.com \
--to=mle+ocaml@mega-nerd.com \
--cc=caml-list@inria.fr \
/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 NNTP newsgroup(s).