From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Original-To: caml-list@sympa.inria.fr Delivered-To: caml-list@sympa.inria.fr Received: from mail2-relais-roc.national.inria.fr (mail2-relais-roc.national.inria.fr [192.134.164.83]) by sympa.inria.fr (Postfix) with ESMTPS id 168B07F75C for ; Wed, 10 Sep 2014 21:14:19 +0200 (CEST) Received-SPF: None (mail2-smtp-roc.national.inria.fr: no sender authenticity information available from domain of drupyog+caml@zoho.com) identity=pra; client-ip=74.201.84.156; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="drupyog+caml@zoho.com"; x-sender="drupyog+caml@zoho.com"; x-conformance=sidf_compatible Received-SPF: Pass (mail2-smtp-roc.national.inria.fr: domain of drupyog+caml@zoho.com designates 74.201.84.156 as permitted sender) identity=mailfrom; client-ip=74.201.84.156; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="drupyog+caml@zoho.com"; x-sender="drupyog+caml@zoho.com"; x-conformance=sidf_compatible; x-record-type="v=spf1" Received-SPF: None (mail2-smtp-roc.national.inria.fr: no sender authenticity information available from domain of postmaster@sender1.zohomail.com) identity=helo; client-ip=74.201.84.156; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="drupyog+caml@zoho.com"; x-sender="postmaster@sender1.zohomail.com"; x-conformance=sidf_compatible X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Aj4BAMOiEFRKyVScm2dsb2JhbABfg2DLG4dDCgGBEhYQAQEBAQEGCwsJFCqEBAEFMgEFCwE0Aw4LIRYPCQMCAQIBRQYBDAgBAYgpAQMBBAwECahshgACiG4iKCWGQAEQAwSPVIRMAZJNgzCHA4I2hQ2RWWqCTwEBAQ X-IPAS-Result: Aj4BAMOiEFRKyVScm2dsb2JhbABfg2DLG4dDCgGBEhYQAQEBAQEGCwsJFCqEBAEFMgEFCwE0Aw4LIRYPCQMCAQIBRQYBDAgBAYgpAQMBBAwECahshgACiG4iKCWGQAEQAwSPVIRMAZJNgzCHA4I2hQ2RWWqCTwEBAQ X-IronPort-AV: E=Sophos;i="5.04,500,1406584800"; d="scan'208";a="94019525" Received: from sender1.zohomail.com ([74.201.84.156]) by mail2-smtp-roc.national.inria.fr with ESMTP; 10 Sep 2014 21:14:03 +0200 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=zapps768; d=zoho.com; h=message-id:date:from:user-agent:mime-version:to:subject:references:in-reply-to:content-type; b=RpfG1uYVpBnhFnUT2M4M/OYpPjvoOeS5DcUx3OYkEwRanahAC7/r/ggU7Bu3Z1RIGhIirNGdmyl4 AJtk5KdNy42z+x2cZtp71jv1HpksNAlgAj6QtRpkXGkraFfjzlUW Received: from [192.168.42.188] (37.163.66.48 [37.163.66.48]) by mx.zohomail.com with SMTPS id 14103764400988.691683827760016; Wed, 10 Sep 2014 12:14:00 -0700 (PDT) Message-ID: <5410A2F5.4070107@zoho.com> Date: Wed, 10 Sep 2014 21:13:57 +0200 From: Drup User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.1.0 MIME-Version: 1.0 To: Maxence Guesdon , caml-list@inria.fr References: <5410522E.3050207@inria.fr> <20140910161744.5a7eecd0@alcazar2> In-Reply-To: <20140910161744.5a7eecd0@alcazar2> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 8bit X-ZohoMailClient: External X-Zoho-Virus-Status: 2 Subject: Re: [Caml-list] One build system to rule them all? Le 10/09/2014 16:17, Maxence Guesdon a écrit : > I can't resist to add good old Make to the list, not specific to OCaml, > yet powerful enough and known by a lot of developers. > No. Every single makefile to compile ocaml (except OCaml-makefile[1]) I have encountered are broken. Every single one of them. OCaml compilation process is too complex to be able to fire some rules and be done with it; especially if you want portability. Please, don't write makefiles. [1]: https://github.com/mmottl/ocaml-makefile