From: "Soegtrop, Michael" <michael.soegtrop@intel.com>
To: Alain Frisch <alain@frisch.fr>,
"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 12:46:30 +0000 [thread overview]
Message-ID: <0F7D3B1B3C4B894D824F5B822E3E5A172CE3377B@IRSMSX102.ger.corp.intel.com> (raw)
In-Reply-To: <562DF227.3060007@frisch.fr>
Dear Alain,
> 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
I see. Well I can't say I fully understand what the problem is, but then I don't need to understand everything. I just asked because flexdll results, as described, in some build trouble and I wanted to make sure that what you get from it is worth this trouble. I take your word that this is the case.
Best regards,
Michael
Intel Deutschland GmbH
Registered Address: Am Campeon 10-12, 85579 Neubiberg, Germany
Tel: +49 89 99 8853-0, www.intel.de
Managing Directors: Christin Eisenschmid, Prof. Dr. Hermann Eul
Chairperson of the Supervisory Board: Tiffany Doon Silva
Registered Office: Munich
Commercial Register: Amtsgericht Muenchen HRB 186928
prev parent reply other threads:[~2015-10-26 12:46 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
2015-10-26 12:46 ` Soegtrop, Michael [this message]
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=0F7D3B1B3C4B894D824F5B822E3E5A172CE3377B@IRSMSX102.ger.corp.intel.com \
--to=michael.soegtrop@intel.com \
--cc=alain@frisch.fr \
--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