caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Alain Frisch <alain@frisch.fr>
To: David Allsopp <dra-news@metastack.com>
Cc: "'caml users'" <caml-list@inria.fr>
Subject: Re: [Caml-list] OCaml version 3.11.0+beta1
Date: Thu, 16 Oct 2008 15:08:58 +0200	[thread overview]
Message-ID: <48F73CEA.7070007@frisch.fr> (raw)
In-Reply-To: <313592F47439468A85341BFF33508587@countertenor>

David Allsopp wrote:
> The install target of flexdll's Makefile suggests copying:
> 
> flexdll_initer.c, flexdll.c
> 	Surely these aren't needed once it's compiled?

Indeed. However, some people might want to recompile them (e.g. to keep 
debug symbols, or to use a specific version of their C compiler).

> 
> cmdline.o, coff.o, reloc.o, version.o
> 	Aren't these all part of flexlink.exe and therefore not needed?

As far as I can tell, the install target does not copy these files.

> default.manifest
> 	Is this necessary for a MinGW build?

No.

> There seems to be an interesting chicken-and-egg source dependency between
> flexdll and OCaml 3.11 - you can't build OCaml 3.11 from source or use it
> afterwards without flexdll and you can't build flexdll from source without
> OCaml. Doesn't that suggest a binary copy of flexdll should be included in
> OCaml's boot directory? All of the other *binary* dependencies for Windows
> OCaml don't require OCaml themselves... just a thought!

You're right about the circular dependency, but the answer is much 
simpler than for the chicken-and-egg question: OCaml came first.
I don't see a compelling reason to include a binary version of flexdll 
in the OCaml distribution. Just consider flexdll as an external 
dependency that comes in binary form (like the MS C compiler). It just 
happens to be produced by the OCaml compiler.

Note that flexlink.exe can be compiler with an old OCaml compiler. Also, 
if you insist to bootstrap everything, it shouldn't be too difficult to 
get a minimal (=no dynamic linking of external C code) ocamlrun.exe for 
3.11 that does not require flexlink.



-- Alain


  reply	other threads:[~2008-10-16 13:09 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-15 13:40 Damien Doligez
2008-10-15 14:19 ` [Caml-list] " Dario Teixeira
2008-10-15 14:55 ` Andres Varon
2008-10-15 15:04   ` Alain Frisch
2008-10-15 15:18     ` Andres Varon
2008-10-15 15:37       ` Alain Frisch
2008-10-15 15:44         ` Andres Varon
2008-10-15 15:46           ` Alain Frisch
2008-10-15 15:22     ` Daniel Bünzli
2008-10-15 15:27       ` Andres Varon
2008-10-15 17:41         ` Daniel Bünzli
2008-10-15 15:32       ` Alain Frisch
2008-10-15 15:56         ` Andres Varon
2008-10-15 16:03           ` Xavier Leroy
2008-10-15 19:39             ` Andres Varon
2008-10-15 15:29     ` Stefano Zacchiroli
2008-10-15 15:32 ` Jaap Boender
2008-10-15 18:07 ` Richard Jones
2008-10-16  8:20 ` David Allsopp
2008-10-17 15:53   ` Xavier Leroy
2008-10-16  9:58 ` David Allsopp
2008-10-16 13:08   ` Alain Frisch [this message]
2008-10-16 15:42     ` Re : " Adrien
2008-10-16 16:00       ` Alain Frisch
2008-10-16  9:58 ` David Allsopp
2008-10-16 16:22   ` Andres Varon
2008-10-16 16:31     ` Andres Varon
2008-10-16 16:50       ` Andres Varon

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=48F73CEA.7070007@frisch.fr \
    --to=alain@frisch.fr \
    --cc=caml-list@inria.fr \
    --cc=dra-news@metastack.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).