caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: "Daniel Bünzli" <daniel.buenzli@erratique.ch>
To: David Allsopp <dra-news@metastack.com>
Cc: "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 01:38:36 +0200	[thread overview]
Message-ID: <660235A830144A6DB09C9B6A0538E5EF@erratique.ch> (raw)
In-Reply-To: <E51C5B015DBD1348A1D85763337FB6D9E4EF5FAC@Remus.metastack.local>



Le samedi, 12 avril 2014 à 00:33, David Allsopp a écrit :

> Windows can't do anything with that. However, most people compiling OCaml packages on Windows expect to use bash (either from Cygwin or MSYS), where the scripts would run as on Unix. Are you sure that Windows compatibility is already a problem?

No, I just thought that you wouldn't get a shell on windows. So maybe you are right, nothing needs to be done, reports welcome.

That being said with an ocaml rewrite I'd abstract the thing a little bit more to make it more DRY (I deliberately prevented myself of doing that in sh: possible but guaranteed to become un-rereadable once you figured out the magic invocations)
  
> s long as you don't do anything exotic with command line parameters (quoting can be very weird for the Windows command processor, cmd, which is what Sys.command uses) then yes, Sys.command will be fine, and the same as on Unix.

Ok and ocamlbuild is ocamlbuild not ocamlbuild.exe ?

> In passing, it does have to be said that getting Windows support automatically from your build system is something that OASIS does...
At an unacceptable time cost, level of complexity and insulation from your build system… oasis maybe fine if you distribute a single package and have time to loose fighting with the system. It's not when you formally release a dozen of packages (and plan to release more).  

At the risk of repeating myself I need simple, reliable, efficient release and packaging workflows: right now if I need to perform a 5 min administrative task on each of my released packages that's already an hour of my time that is gone and I hate admin tasks. So it turns out that in *my* case, I'm very well served by opam .install files, ocamlbuild and a 100 loc, trivial, shell script [1] that I hope I'll be able to kill if we once get a good build system that has decent packaging support and handles .install file generation for me.

Best,

Daniel

[1] https://github.com/dbuenzli/pkgopkg/blob/master/pkg/pkg-builder



  reply	other threads:[~2014-04-11 23:39 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 [this message]
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
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=660235A830144A6DB09C9B6A0538E5EF@erratique.ch \
    --to=daniel.buenzli@erratique.ch \
    --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).