From: Jeremy Yallop <yallop@gmail.com>
To: Dan Benjamin <dbenjamin@janestreet.com>
Cc: David Sheets <sheets@alum.mit.edu>,
Bruno Deferrari <utizoc@gmail.com>, O Caml <caml-list@inria.fr>
Subject: Re: [Caml-list] Static linking via Ctypes?
Date: Tue, 25 Mar 2014 21:19:47 +0000 [thread overview]
Message-ID: <CAAxsn=GfRQe1Xph32HVQxZUNu-8KH3YtV9jOZBjguU8-43Up_w@mail.gmail.com> (raw)
In-Reply-To: <CACKEwpa4ypJQUHgsYzG1ftTCAjf5FX6rGsrok-UuDqNiRdif2Q@mail.gmail.com>
David Sheets <sheets@alum.mit.edu> wrote:
> I did
>
> <https://github.com/dsheets/ocaml-unix-unistd/blob/master/lib/unix_unistd_stubs.c#L61>
>
> and
>
> <https://github.com/dsheets/ocaml-unix-unistd/blob/master/lib/ctypes/unix_unistd.ml#L32>
>
> to require a static link without stub generation in addition to
> ocamlmklib on the .ml and .o files.
>
> Unfortunately, this is not very portable (or sane).
On 25/03/2014, Dan Benjamin <dbenjamin@janestreet.com> wrote:
> That does work, thanks very much. Are there plans to add anything
> similar to Ctypes?
Not exactly, since the stub generation support in the next ctypes
release resolves these issues in a different way. In the current
release (0.2.3) setting up foreign calls and linking are both entirely
dynamic. Stub generation will make it possible to link statically as
well.
next prev parent reply other threads:[~2014-03-25 21:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-25 14:54 dbenjamin
2014-03-25 15:04 ` Bruno Deferrari
2014-03-25 15:11 ` Dan Benjamin
2014-03-25 15:24 ` David Sheets
2014-03-25 17:55 ` Dan Benjamin
2014-03-25 21:19 ` Jeremy Yallop [this message]
2014-03-25 21:37 ` Milan Stanojević
2014-03-25 23:14 ` Jeremy Yallop
2014-03-26 16:24 ` Travis Brady
2014-03-26 17:17 ` Daniel Bünzli
2014-03-26 17:25 ` Milan Stanojević
2014-03-25 15:10 ` 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='CAAxsn=GfRQe1Xph32HVQxZUNu-8KH3YtV9jOZBjguU8-43Up_w@mail.gmail.com' \
--to=yallop@gmail.com \
--cc=caml-list@inria.fr \
--cc=dbenjamin@janestreet.com \
--cc=sheets@alum.mit.edu \
--cc=utizoc@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).