From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail1-relais-roc.national.inria.fr (mail1-relais-roc.national.inria.fr [192.134.164.82]) by walapai.inria.fr (8.13.6/8.13.6) with ESMTP id pBEAP0nC023812 for ; Wed, 14 Dec 2011 11:25:00 +0100 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AhkBAPB46E7B/BfSkWdsb2JhbABDq0oBAQEBCQsLBxQDIoFyAQEEAThAARALGAkWDwkDAgECATcBDQYNAQcBAYd2Aga3GIwJBJR0hU2MXQ X-IronPort-AV: E=Sophos;i="4.71,351,1320620400"; d="scan'208";a="135351198" Received: from msa01.smtpout.orange.fr (HELO msa.smtpout.orange.fr) ([193.252.23.210]) by mail1-smtp-roc.national.inria.fr with ESMTP; 14 Dec 2011 11:24:55 +0100 Received: from [192.168.1.102] ([83.199.117.71]) by mwinf5d37 with ME id 8yQu1i0021YWU4b03yQu4s; Wed, 14 Dec 2011 11:24:54 +0100 Message-ID: <4EE87976.4030604@frisch.fr> Date: Wed, 14 Dec 2011 11:24:54 +0100 From: Alain Frisch User-Agent: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:8.0) Gecko/20111105 Thunderbird/8.0 MIME-Version: 1.0 To: Jonathan Protzenko CC: Adrien , Martin DeMello , Gerd Stolpmann , caml-list@inria.fr References: <4EDE33A0.6070004@gmail.com> <1323760512.9833.9.camel@samsung> <4EE711FB.5020602@frisch.fr> <4EE83C26.7090108@frisch.fr> <4EE86D90.6080409@gmail.com> In-Reply-To: <4EE86D90.6080409@gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [Caml-list] Some comments on recent discussions On 12/14/2011 10:34 AM, Jonathan Protzenko wrote: >> For the native compiler, we need an external toolchain, but this is >> not a huge issue. With some little amount of work, one could support a >> standalone msys/mingw (as opposed to mingw compilers packaged in Cygwin) > This is precisely what http://protz.github.com/ocaml-installer/ > provides. Is that not what you're describing here? Yes, I guess. Is has been known for some time that the mingw port could be made to work with a standalone mingw compiler at little cost, but the "officially" supported mingw port required Cygwin, and flexdll needs to be adapted a little bit. Providing long-term support for this new setup will take some resource (yet another Windows port!). Alternatively, one could decide that the officially supported "mingw port" is based on a standalone mingw (or mingw-w64); Cygwin packagers could always create OCaml packages for the mingw compilers shipped with Cygwin. This is a big move, which will probably make some people unhappy. >> and it would be interesting to come up with a minimal mingw >> distribution (only with a C compiler, assembler, etc, as required by >> ocamlopt) that could be packaged together with OCaml. > Looks a little bit more involved but not un-feasible. Would you be > interested in helping me maintain such a port? ;-) Yes, I can help solving some specific problems (e.g. with flexdll); but probably not for long-term maintenance. -- Alain