From: Gabriel Scherer <gabriel.scherer@gmail.com>
To: Jeremy Yallop <yallop@gmail.com>
Cc: Goswin von Brederlow <goswin-v-b@web.de>, Caml List <caml-list@inria.fr>
Subject: Re: [Caml-list] ANN: ocaml-ctypes 0.5.0, a library for calling C functions directly from OCaml
Date: Tue, 22 Mar 2016 16:00:07 +0100 [thread overview]
Message-ID: <CAPFanBEQcW-dm0Zfbhr7NG6W0FEO9Y+EKw-C+bTuKBXCz2Qiyg@mail.gmail.com> (raw)
In-Reply-To: <CAAxsn=FEpTjnv0BrZE46e3hpsZuO7paZfYtzr-e6YsONKyb_tQ@mail.gmail.com>
> [flock] has some oasis and ocamlbuild rules for ctypes stub generation.
Maybe it would be a good time for the ctypes+ocamlbuild users to agree
on a set of common rules and distribute them as a separate plugin. (I
wouldn't mind helping on the ocamlbuild part if necessary, but I don't
use ctypes myself.)
On Tue, Mar 22, 2016 at 12:11 PM, Jeremy Yallop <yallop@gmail.com> wrote:
> On 22 March 2016 at 10:20, Goswin von Brederlow <goswin-v-b@web.de> wrote:
>> On Mon, Mar 21, 2016 at 07:42:05PM +0000, Jeremy Yallop wrote:
>>> I'm pleased to announce release 0.5.0 of ocaml-ctypes, which is now
>>> available on OPAM.
>>
>> Does anyone have an example of using ctypes with stub generation using
>> oasis?
>
> OPAM suggests that there are a few:
>
> $ comm -12 <(opam list --short --depends-on oasis) <(opam list --short
> --depends-on ctypes)
> flock
> nocrypto
> ocephes
> sanlock
> tsdl-image
> zstd
>
> Here's the link to the homepage for the first result, which has some
> oasis and ocamlbuild rules for ctypes stub generation:
>
> $ opam show -f homepage flock
> https://github.com/simonjbeaumont/ocaml-flock
>
> --
> Caml-list mailing list. Subscription management and archives:
> https://sympa.inria.fr/sympa/arc/caml-list
> Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
> Bug reports: http://caml.inria.fr/bin/caml-bugs
next prev parent reply other threads:[~2016-03-22 15:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-21 19:42 Jeremy Yallop
2016-03-22 10:12 ` sp
2016-03-22 11:08 ` Jeremy Yallop
2016-03-22 10:20 ` Goswin von Brederlow
2016-03-22 11:11 ` Jeremy Yallop
2016-03-22 15:00 ` Gabriel Scherer [this message]
2016-03-22 15:07 ` Jeremy Yallop
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=CAPFanBEQcW-dm0Zfbhr7NG6W0FEO9Y+EKw-C+bTuKBXCz2Qiyg@mail.gmail.com \
--to=gabriel.scherer@gmail.com \
--cc=caml-list@inria.fr \
--cc=goswin-v-b@web.de \
--cc=yallop@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 NNTP newsgroup(s).