From: "Daniel Bünzli" <daniel.buenzli@erratique.ch>
To: Adrien Nader <adrien@notk.org>
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 14:38:11 +0200 [thread overview]
Message-ID: <74C2E1F54AA349E6899E909804979B72@erratique.ch> (raw)
In-Reply-To: <20140412114145.GA18285@notk.org>
Le samedi, 12 avril 2014 à 13:41, Adrien Nader a écrit :
> 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.
Future-proof is what interests me. In my case the package build script needs a single ocamlbuild invocation and write one (.install) file so that wouldn't be atrocious to manage, there's no cp, mv, install etc, I leave that to my friend opam-installer. Actually I'm interested in rewriting these script in .ml for readability, abstraction and maybe having a more readable command line interface through a handful of combinators and the Arg module. So if these things become ml scripts the cross platform way of invoking them would then just become:
ocaml pkg/build
rather than just
pkg/build
that would take care of the fact that windows wouldn't understand #!/usr/bin/env ocaml ?
Daniel
P.S. Is there any tutorial/instructions that shows us how ocaml development occurs/should be done on windows ? Packager instructions about dos and don'ts would be helpful too.
next prev parent reply other threads:[~2014-04-12 12:38 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
2014-04-12 12:38 ` Daniel Bünzli [this message]
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=74C2E1F54AA349E6899E909804979B72@erratique.ch \
--to=daniel.buenzli@erratique.ch \
--cc=adrien@notk.org \
--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