caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: "Soegtrop, Michael" <michael.soegtrop@intel.com>
To: "Daniel Bünzli" <daniel.buenzli@erratique.ch>
Cc: "caml-list@inria.fr" <caml-list@inria.fr>
Subject: RE: [Caml-list] ocamlbuild on Windows and bash vs. cmd
Date: Thu, 6 Oct 2016 14:15:07 +0000	[thread overview]
Message-ID: <0F7D3B1B3C4B894D824F5B822E3E5A172CF8E210@IRSMSX102.ger.corp.intel.com> (raw)
In-Reply-To: <645B0ADB30534643B7294B43C28A3F3D@erratique.ch>

Dear Daniel,

> See https://github.com/ocaml/ocamlbuild/issues/64

yes, I have seen the discussion, especially the discussion if one should use cmd vs. removing the use of a shell by ocamlbuild entirely. I agree that the latter would be the better solution, but it would be a major change since currently ocamlbuild wraps everything through string commands. But maybe it is not as bad as it looks.

And I take this as a "yes" on the question if something like this would be appreciated by the community.

I am a bit in a hurry to get something working for Coq 8.6. I guess I first make a cmd based hack for Coq and then look into the real solution.

I will continue the discussion on the ocamlbuild issue tracker item linked above.

Best regards,

Michael
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

  reply	other threads:[~2016-10-06 14:16 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 [this message]
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
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=0F7D3B1B3C4B894D824F5B822E3E5A172CF8E210@IRSMSX102.ger.corp.intel.com \
    --to=michael.soegtrop@intel.com \
    --cc=caml-list@inria.fr \
    --cc=daniel.buenzli@erratique.ch \
    /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).