caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Adrien Nader <adrien@notk.org>
To: "Daniel Bünzli" <daniel.buenzli@erratique.ch>
Cc: David Allsopp <dra-news@metastack.com>,
	"caml-list@inria.fr" <caml-list@inria.fr>
Subject: Re: [Caml-list] OCaml script on windows (was Re: [ANN] React 1.0.0)
Date: Sat, 12 Apr 2014 13:41:45 +0200	[thread overview]
Message-ID: <20140412114145.GA18285@notk.org> (raw)
In-Reply-To: <CB34F8DD4D554EBBA9159DFF6E611B27@erratique.ch>

On Sat, Apr 12, 2014, Daniel Bünzli wrote:
> 
> 
> Le samedi, 12 avril 2014 à 09:44, Adrien Nader a écrit :
> 
> > Sorry, forgot to mention that this included building software through
> > oasis and ocamlbuild. From configure of libraries to build the final
> > executable. And that has been the case for 3 years at least.
> 
> Does that change his answer (i.e. that a shell interpreter will be available) ?

The requirements for ocamlbuild on windows _right_ _now_ include
bash.exe (not "sh" iirc) because of Sys.command (!) and a few tools like
cp, mv, find, mkdir.

This is far from enough for typical shell scripting and probably barely
enough for shell scripts which are carefully crafted to rely as little
as possible on anything that isn't a shell builtin. This looks like a
dead-end to me.

Moreover, the reliance on mv, cp and friends in ocamlbuild is probably
only justified by the need to have a (ba)sh.exe anyway. If this
requirement goes away, I expect the other shell-outs to go away too.

This isn't very high in the todo list for ocamlbuild and  but it would
simplify some OCaml installations on Windows and would make builds much
much faster (spawning processes in Cygwin/Msys is very slow since they
emulate fork without kernel support).

In a few words, today you can expect a posix shell but this isn't very
future-proof. However I'd probably not change much the current build
system: process management in OCaml is more work than in shell and a
arewrite would take time for little benefit, all while the environment
is evolving rapidly.

-- 
Adrien Nader

  reply	other threads:[~2014-04-12 11:41 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-02 16:01 [Caml-list] [ANN] React 1.0.0 Daniel Bünzli
2014-04-08  1:04 ` Daniel Bünzli
2014-04-11 15:12   ` Markus Weißmann
2014-04-11 15:58     ` Daniel Bünzli
2014-04-11 16:05       ` Anil Madhavapeddy
2014-04-11 16:32         ` Daniel Bünzli
2014-04-11 16:59           ` [Caml-list] OCaml script on windows (was Re: [ANN] React 1.0.0) Daniel Bünzli
2014-04-11 22:33             ` David Allsopp
2014-04-11 23:38               ` Daniel Bünzli
2014-04-15 19:21                 ` [Caml-list] topkg (was Re: OCaml script on windows (was Re: [ANN] React 1.0.0)) Daniel Bünzli
2014-04-12  7:39               ` [Caml-list] OCaml script on windows (was Re: [ANN] React 1.0.0) Adrien Nader
2014-04-12  7:44                 ` Adrien Nader
2014-04-12 10:14                   ` Daniel Bünzli
2014-04-12 11:41                     ` Adrien Nader [this message]
2014-04-12 12:38                       ` Daniel Bünzli
2014-04-13  9:21                         ` Adrien Nader
2014-04-13  9:31                           ` Anil Madhavapeddy
2014-04-13 11:17                             ` Adrien Nader
2014-04-13 12:33                               ` Daniel Bünzli
2014-04-21 18:18   ` [Caml-list] [ANN] React 1.0.1 Daniel Bünzli
2014-04-27 20:33     ` [Caml-list] [ANN] React 1.1.0 Daniel Bünzli
2014-05-04 23:16       ` 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=20140412114145.GA18285@notk.org \
    --to=adrien@notk.org \
    --cc=caml-list@inria.fr \
    --cc=daniel.buenzli@erratique.ch \
    --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).