From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail4-relais-sop.national.inria.fr (mail4-relais-sop.national.inria.fr [192.134.164.105]) by walapai.inria.fr (8.13.6/8.13.6) with ESMTP id pBENsJYH018679 for ; Thu, 15 Dec 2011 00:54:19 +0100 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Ak8BAAQ26U7RVde2kGdsb2JhbABEqxYIIgEBAQEJCQ0HFAQhgXIBAQEEEgIsARsUCQEDDAYFCwMKLiIBEQEFARwGEyKiJgqLZIJrhGhAiHECBQuLfASIMoxCjXU9hBk X-IronPort-AV: E=Sophos;i="4.71,355,1320620400"; d="scan'208";a="123405406" Received: from mail-ey0-f182.google.com ([209.85.215.182]) by mail4-smtp-sop.national.inria.fr with ESMTP/TLS/RC4-SHA; 15 Dec 2011 00:54:13 +0100 Received: by eaaf13 with SMTP id f13so2392814eaa.27 for ; Wed, 14 Dec 2011 15:54:13 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=G5cNFIqdS5Yxv1euOrXuzZbxhG1jdbGaOwJ7WwM7StI=; b=AjELJmgd6I5VQprGdA/wrE0ywhBtKHPNX4tDQtS8/61cljGXztW8hEHYV/ZxIj0L8j VOByguo4z/9NNbGvP/l0s5m16uV1Iq55RIiNzVnswQ2ISlOZxi3X0S18sDsyfmX1d838 DthavVGXfziEAyvyNOLD+IJHcwtir3GdzdLr0= MIME-Version: 1.0 Received: by 10.205.138.20 with SMTP id iq20mr167888bkc.86.1323906853216; Wed, 14 Dec 2011 15:54:13 -0800 (PST) Received: by 10.204.226.65 with HTTP; Wed, 14 Dec 2011 15:54:13 -0800 (PST) In-Reply-To: <1323867161.7750.27.camel@samsung> References: <4EDE33A0.6070004@gmail.com> <1323760512.9833.9.camel@samsung> <4EE711FB.5020602@frisch.fr> <4EE83C26.7090108@frisch.fr> <1323867161.7750.27.camel@samsung> Date: Wed, 14 Dec 2011 15:54:13 -0800 Message-ID: From: Martin DeMello To: Gerd Stolpmann Cc: Alain Frisch , Adrien , Jonathan Protzenko , caml-list@inria.fr Content-Type: text/plain; charset=ISO-8859-1 Subject: Re: [Caml-list] Some comments on recent discussions On Wed, Dec 14, 2011 at 4:52 AM, Gerd Stolpmann wrote: > > There could be an alternative: The "busybox approach". We could develop > a toolkit that covers all the Unix commands we need for the existing > build scripts. It would include easy things like cp, mv etc., but also a > classic "make" (medium difficulty, note that it could reuse the > godi_make code), and especially a POSIX shell. The latter is a bit of > work, but not too much. I'd guess the overall effort takes not more than > 1-2 weeks if done by somebody how knows the semantics of the tools very > well. does mingw+msys not already do this? the last time i checked, it shipped with rxvt, bash and bunch of natively compiled standard posix utilities. martin