From: "Soegtrop, Michael" <michael.soegtrop@intel.com>
To: Gerd Stolpmann <info@gerd-stolpmann.de>,
Jeremie Dimino <jdimino@janestreet.com>
Cc: "caml-list@inria.fr" <caml-list@inria.fr>
Subject: RE: [Caml-list] ocamlbuild on Windows and bash vs. cmd
Date: Fri, 7 Oct 2016 06:58:45 +0000 [thread overview]
Message-ID: <0F7D3B1B3C4B894D824F5B822E3E5A172CF8E462@IRSMSX102.ger.corp.intel.com> (raw)
In-Reply-To: <1475780165.16332.8.camel@gerd-stolpmann.de>
Dear Gerd, Jeremie,
I agree, something like a very simple shell which gets its commands and redirections described as some sort of AST is likely the easiest to port and most robust solution.
I will look into Jeremie's development and omake and see if it is from a technical and licensing point of view reusable for ocamlbuild.
Best Regards,
Michael
> -----Original Message-----
> From: Gerd Stolpmann [mailto:info@gerd-stolpmann.de]
> Sent: Thursday, October 06, 2016 8:56 PM
> To: Jeremie Dimino; Soegtrop, Michael
> Cc: caml-list@inria.fr
> Subject: Re: [Caml-list] ocamlbuild on Windows and bash vs. cmd
>
> This is also what omake does. Pipes, redirections, and even a number of
> commands like rm, cp, ls are completely implemented inside omake, so that
> everything works on Unix and Windows the same. I guess this is the only way
> to get to a uniform build system, at least if you don't want to depend on 3rd-
> party tools like Cygwin.
>
> Gerd
>
> Am Donnerstag, den 06.10.2016, 18:45 +0100 schrieb Jeremie Dimino:
> > I don't have an opinion on using cmd in ocamlbuild, but I have been
> > looking at similar things for jenga recently. With jenga the actions
> > generated by the rules are of the form (prog, args) and when one wants
> > to to do something more complicated, they have to manually build a
> > shell command. In the Jane Street rules we are using bash.
> >
> > Going through bash is often frustrating, even on Unix. Moreover for
> > the public release of Jane Street packages I'd like to avoid relying
> > too much on bash as it has often been a source of problems in the
> > past.
> >
> > The solution I'm aimed at is to have the jenga rules produce actions
> > using a small DSL allowing pipes and other things and interpret this
> > DSL without the use of a third-party shell, i.e. just using system
> > calls and threads.
> >
> > It's still a work in progress but I already have the backend part
> > working [1]. It's aimed at being portable on Windows. The code for
> > Windows is written but not yet tested, I plan to do it at some point.
> >
> > I imagine that it shouldn't be too use this in ocamlbuild if the [Sh]
> > constructor was removed and replaced by a few other constructors to
> > express pipes, redirections, etc...
> >
> > [1] https://github.com/janestreet/shexp
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, Christian Lamprechter
Chairperson of the Supervisory Board: Nicole Lau
Registered Office: Munich
Commercial Register: Amtsgericht Muenchen HRB 186928
next prev parent reply other threads:[~2016-10-07 7:00 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-06 13:38 Soegtrop, Michael
2016-10-06 13:45 ` Kakadu
2016-10-06 14:01 ` Soegtrop, Michael
2016-10-06 13:55 ` Daniel Bünzli
2016-10-06 14:15 ` Soegtrop, Michael
2016-10-06 14:45 ` Gabriel Scherer
2016-10-06 16:16 ` Soegtrop, Michael
2016-10-06 17:45 ` Jeremie Dimino
2016-10-06 18:56 ` Gerd Stolpmann
2016-10-07 6:58 ` Soegtrop, Michael [this message]
2016-10-07 16:19 ` Yaron Minsky
2016-10-11 11:49 ` Soegtrop, Michael
2016-10-11 12:36 ` Yaron Minsky
2016-10-11 13:00 ` Ivan Gotovchits
2016-10-11 13:06 ` Anil Madhavapeddy
2016-10-11 13:13 ` Yaron Minsky
2016-10-11 13:27 ` Hendrik Boom
2016-10-11 13:53 ` Soegtrop, Michael
2016-10-11 15:48 ` Adrien Nader
2016-10-11 13:46 ` Soegtrop, Michael
2016-10-14 12:19 ` Manfred Lotz
2016-10-17 8:08 ` Soegtrop, Michael
2016-10-17 9:22 ` Manfred Lotz
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=0F7D3B1B3C4B894D824F5B822E3E5A172CF8E462@IRSMSX102.ger.corp.intel.com \
--to=michael.soegtrop@intel.com \
--cc=caml-list@inria.fr \
--cc=info@gerd-stolpmann.de \
--cc=jdimino@janestreet.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