I very much hope the licensing isn't an issue. We purposely picked a very liberal license to make this kind of thing as easy as possible. Do tell us if you find an issue there.

y

On Fri, Oct 7, 2016 at 8:58 AM, Soegtrop, Michael <michael.soegtrop@intel.com> wrote:
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

--
Caml-list mailing list.  Subscription management and archives:
https://sympa.inria.fr/sympa/arc/caml-list
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
Bug reports: http://caml.inria.fr/bin/caml-bugs