Mailing list for all users of the OCaml language and system.
 help / color / mirror / Atom feed
From: Alain Frisch <alain@frisch.fr>
To: "Soegtrop, Michael" <michael.soegtrop@intel.com>,
	"caml-list@inria.fr" <caml-list@inria.fr>
Subject: Re: [Caml-list] flexdll circular dependency on ocamlc: Impossible to built ocaml for mingw without using some prebuilt binaries?
Date: Mon, 26 Oct 2015 10:28:07 +0100	[thread overview]
Message-ID: <562DF227.3060007@frisch.fr> (raw)
In-Reply-To: <0F7D3B1B3C4B894D824F5B822E3E5A172CE33610@IRSMSX102.ger.corp.intel.com>

On 26/10/2015 10:13, Soegtrop, Michael wrote:
> Dear Alain,
>
>> Dynlink follows a different model: dynlinked units are not tied to a specific
>> main executable.  A myplugin.cmxs can be dynamically linked by any
>> application that provides the required interfaces.
>
> Can you explain what you mean by Dynlink (or point me to some documents)? I though we are talking about loading DLLs with LoadLibrary programmatically (rather than by the image loader). I am quite sure calling main executable functions from a DLL loaded this way does work. But I am not sure we are talking about this mechanism or something else.

I'm talking about the Dynlink library which allows OCaml code to 
dynamically load plugins (made of OCaml + perhaps native code).  The 
loaded code is compiled in the same way as if it were to be linked in 
the main program, but then it is linked into a .cmxs file (which is 
really a dll).

http://caml.inria.fr/pub/docs/manual-ocaml/libref/Dynlink.html

Alain

  reply	other threads:[~2015-10-26  9:28 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-24  9:50 Soegtrop, Michael
2015-10-24 11:33 ` David Allsopp
2015-10-26  8:54   ` Soegtrop, Michael
2015-10-24 12:13 ` Alain Frisch
2015-10-24 12:51   ` David Allsopp
2015-10-26  9:41     ` Alain Frisch
2015-10-26 11:13       ` David Allsopp
2015-10-26  9:13   ` Soegtrop, Michael
2015-10-26  9:28     ` Alain Frisch [this message]
2015-10-26 12:46       ` Soegtrop, Michael

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=562DF227.3060007@frisch.fr \
    --to=alain@frisch.fr \
    --cc=caml-list@inria.fr \
    --cc=michael.soegtrop@intel.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