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 D5D767F860 for ; Sat, 22 Feb 2014 15:30:36 +0100 (CET) Received-SPF: None (mail2-smtp-roc.national.inria.fr: no sender authenticity information available from domain of adrien@notk.org) identity=pra; client-ip=91.121.71.147; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="adrien@notk.org"; x-sender="adrien@notk.org"; x-conformance=sidf_compatible Received-SPF: Pass (mail2-smtp-roc.national.inria.fr: domain of adrien@notk.org designates 91.121.71.147 as permitted sender) identity=mailfrom; client-ip=91.121.71.147; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="adrien@notk.org"; x-sender="adrien@notk.org"; 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@nautica.notk.org) identity=helo; client-ip=91.121.71.147; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="adrien@notk.org"; x-sender="postmaster@nautica.notk.org"; x-conformance=sidf_compatible X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AgMFAPuzCFNbeUeT/2dsb2JhbABagwY7g1q9RoEKFnSCJQEBBAEjDwFGBQsLGAICBRMOAgIPBRgxiBAMCahDoRUXgSmNOweCbzWBFASYMwGSJ4MuOw X-IPAS-Result: AgMFAPuzCFNbeUeT/2dsb2JhbABagwY7g1q9RoEKFnSCJQEBBAEjDwFGBQsLGAICBRMOAgIPBRgxiBAMCahDoRUXgSmNOweCbzWBFASYMwGSJ4MuOw X-IronPort-AV: E=Sophos;i="4.97,523,1389740400"; d="scan'208";a="59726903" Received: from nautica.notk.org ([91.121.71.147]) by mail2-smtp-roc.national.inria.fr with ESMTP/TLS/ADH-AES256-SHA; 22 Feb 2014 15:30:36 +0100 Received: by nautica.notk.org (Postfix, from userid 1003) id 86CC7C009; Sat, 22 Feb 2014 15:30:35 +0100 (CET) Date: Sat, 22 Feb 2014 15:30:35 +0100 From: Adrien Nader To: =?utf-8?Q?Beno=C3=AEt?= Vaugon Cc: caml-list@inria.fr Message-ID: <20140222143035.GB19246@notk.org> References: <20140218185032.GA20593@notk.org> <5306330F.1020401@inria.fr> <20140221075326.GC7924@notk.org> <53073EFA.2020501@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <53073EFA.2020501@gmail.com> User-Agent: Mutt/1.5.21 (2010-09-15) Subject: Re: [Caml-list] [RFC] Remaining changes for cross-compilation support in OCaml On Fri, Feb 21, 2014, Benoît Vaugon wrote: > Hi, > > For cross-compilation, have you seen opam cross-compiler packages > for win32 and win64: > https://github.com/vouillon/opam-windows-repository, and for > android: https://github.com/vouillon/opam-android-repository? These > repositories also provide opam packages for some cross-compiled > libraries, which is not simple because it requires both the host > ocaml compilers and the cross-ones. Itmight be interesting to > combineour efforts... I had been pointed to them a few months ago. From what I can tell, these patches to the compiler cannot be integrated upstream; they require "manual" steps like "make -C dir/ foo && mv bar baz && make -C dir2" and a few changes which can only apply to windows targets. By the way, the patches I've worked on were not started by me. However I cannot trace their path properly; as far as I can tell, they were started in Fedora, then went through debian and then mxe.cc. Looking at these pages, I notice that I forgot one component for the patches: ocamlfind and build system integration. IOW, how to cross-build libraries. I'll add that to the RFC. > As with your compiler, linking bytecode with -custom doesn't work > with these compilers too, due to the same reason. Actually, the patches I have make it possible to link bytecode with -custom; it's simply that the test that would fail for cross-compilation is skipped. -- Adrien Nader