Mailing list for all users of the OCaml language and system.
 help / color / mirror / Atom feed
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 09:13:46 +0000	[thread overview]
Message-ID: <0F7D3B1B3C4B894D824F5B822E3E5A172CE33610@IRSMSX102.ger.corp.intel.com> (raw)
In-Reply-To: <562B75D7.1000900@frisch.fr>

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.

> As for the dependency between OCaml and flexdll: the simplest approach is
> to consider flexdll as any other external tool required to build OCaml (do you
> recompile "gcc", "make", etc  from sources?).

The idea of open source is that you have the possibility to fix bugs yourself. This can be an important factor for maintainability. I am quite sure I can compile gcc from sources if I want to. Everything where I am not so sure where it comes from and how it is build I actually do build from sources. This includes things which are as nasty to build as GTK.

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


  parent reply	other threads:[~2015-10-26  9:13 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 [this message]
2015-10-26  9:28     ` Alain Frisch
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=0F7D3B1B3C4B894D824F5B822E3E5A172CE33610@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