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 mail3-relais-sop.national.inria.fr (mail3-relais-sop.national.inria.fr [192.134.164.104]) by sympa.inria.fr (Postfix) with ESMTPS id BC93D7F91C for ; Tue, 24 May 2016 08:57:40 +0200 (CEST) IronPort-PHdr: 9a23:WLvN/RRs+K1XqepA9O29YZqy+dpsv+yvbD5Q0YIujvd0So/mwa65ZBCN2/xhgRfzUJnB7Loc0qyN4/GmBTRLvcrJmUtBWaIPfidNsd8RkQ0kDZzNImzAB9muURYHGt9fXkRu5XCxPBsdMs//Y1rPvi/6tmZKSV3BPAZ4bt74BpTVx5zukbviqtuPO04U2HKUWvBbElaflU3prM4YgI9veO4a6yDihT92QdlQ3n5iPlmJnhzxtY+a9Z9n9DlM6bp6r5YTGY2zRakzTKRZATI6KCh1oZSz7ViQcBGLrkc4fi1Wy0cJUED560SwZZD8vTfgsfI5kAybNs3/QLR+EWCn7qxrQRLszjwAOjEl6mbPos12kK9f5hmmokos7ZTTZdSKNPtic7rAdMkZDT5eXsdNWjVcC5m/R5QPDvYMJPtRtYq7oEEB+0jtTTKwDf/in2cbzkT92rc3hqFxTAw= Authentication-Results: mail3-smtp-sop.national.inria.fr; spf=None smtp.pra=whitequark@whitequark.org; spf=Pass smtp.mailfrom=whitequark@whitequark.org; spf=None smtp.helo=postmaster@mail.whitequark.org Received-SPF: None (mail3-smtp-sop.national.inria.fr: no sender authenticity information available from domain of whitequark@whitequark.org) identity=pra; client-ip=176.58.103.125; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="whitequark@whitequark.org"; x-sender="whitequark@whitequark.org"; x-conformance=sidf_compatible Received-SPF: Pass (mail3-smtp-sop.national.inria.fr: domain of whitequark@whitequark.org designates 176.58.103.125 as permitted sender) identity=mailfrom; client-ip=176.58.103.125; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="whitequark@whitequark.org"; x-sender="whitequark@whitequark.org"; x-conformance=sidf_compatible; x-record-type="v=spf1" Received-SPF: None (mail3-smtp-sop.national.inria.fr: no sender authenticity information available from domain of postmaster@mail.whitequark.org) identity=helo; client-ip=176.58.103.125; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="whitequark@whitequark.org"; x-sender="postmaster@mail.whitequark.org"; x-conformance=sidf_compatible X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: A0CvBACW+kNX/31nOrBbhA2DcrkMGoV3AoFsEAEBAQEBAQEBZCeCLYIVAQEBBDgCPxAEBwkPLiwrBhuIK8QrAQEBAQYCASSGJoMugR+KGQWXcUaCHYNjiBmPI49MNyuDbTyKAwEBAQ X-IPAS-Result: A0CvBACW+kNX/31nOrBbhA2DcrkMGoV3AoFsEAEBAQEBAQEBZCeCLYIVAQEBBDgCPxAEBwkPLiwrBhuIK8QrAQEBAQYCASSGJoMugR+KGQWXcUaCHYNjiBmPI49MNyuDbTyKAwEBAQ X-IronPort-AV: E=Sophos;i="5.26,359,1459807200"; d="scan'208";a="178780557" Received: from fehu.whitequark.org (HELO mail.whitequark.org) ([176.58.103.125]) by mail3-smtp-sop.national.inria.fr with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 24 May 2016 08:57:40 +0200 Received: by mail.whitequark.org (Postfix, from userid 33) id BFF4F10CA78; Tue, 24 May 2016 06:57:38 +0000 (UTC) To: "Soegtrop, Michael" X-PHP-Originating-Script: 1000:rcube.php MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Tue, 24 May 2016 06:57:38 +0000 From: whitequark Cc: caml-list@inria.fr In-Reply-To: <0F7D3B1B3C4B894D824F5B822E3E5A172CF04CA0@IRSMSX102.ger.corp.intel.com> References: <9D53A509-55BC-4E89-A8CF-389EE20580DD@hms.harvard.edu> <77d8e9183ed929e80464c70376561cd8@whitequark.org> <0F7D3B1B3C4B894D824F5B822E3E5A172CF04CA0@IRSMSX102.ger.corp.intel.com> Message-ID: <523de93ae2fdfcafd18686809b09d84e@whitequark.org> X-Sender: whitequark@whitequark.org User-Agent: Roundcube Webmail/1.1.5 Subject: RE: [Caml-list] [ANN] opam-cross-windows On 2016-05-23 08:24, Soegtrop, Michael wrote: > Dear whitequark, > >> My repository uses MXE so that a wide range of native dependencies can >> be >> easily compiled. Moreover, you get opam-cross-android and >> opam-cross-ios >> for free, with exact same conventions, largely similar package sets, >> etc, and >> it is easy to port packages between the three as well. > > Thanks for the pointer to MXE (http://mxe.cc/). A very interesting > project! It might help to put MinGW cross opam for cygwin on a solid > foundation. > > One question: how happy are you with the make file approach of MXE? I > worked an something similar as MXE, but based on shell scripts, since > I thought "meta makefiles" might be hard to maintain and to debug and > shell scripts might be more appropriate for this task. But it was a > difficult decision and I still see some advantages in using make for > this. I have absolutely none in-depth understanding of how MXE functions, but I can say that I never needed one, or wanted it, so I'd say it is a success :) Of course, this is only valid from the perspective of a user. -- whitequark