From: Adrien Nader <adrien@notk.org>
To: "Benoît Vaugon" <benoit.vaugon@gmail.com>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] [RFC] Remaining changes for cross-compilation support in OCaml
Date: Sat, 22 Feb 2014 15:30:35 +0100 [thread overview]
Message-ID: <20140222143035.GB19246@notk.org> (raw)
In-Reply-To: <53073EFA.2020501@gmail.com>
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
next prev parent reply other threads:[~2014-02-22 14:30 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-18 18:50 Adrien Nader
2014-02-19 9:51 ` [Caml-list] [RFC] Remaining changes for cross-compilation support oleg
2014-02-20 11:03 ` [Caml-list] [RFC] Remaining changes for cross-compilation support in OCaml Goswin von Brederlow
2014-02-21 7:19 ` Adrien Nader
2014-02-20 16:53 ` Xavier Leroy
2014-02-21 0:06 ` Anil Madhavapeddy
2014-02-21 7:06 ` Adrien Nader
2014-02-21 1:44 ` Francois Berenger
2014-02-21 7:53 ` Adrien Nader
2014-02-21 11:56 ` Benoît Vaugon
2014-02-21 12:52 ` Mark Shinwell
2014-02-22 14:17 ` Adrien Nader
2014-02-22 14:30 ` Adrien Nader [this message]
2014-02-22 15:16 ` Gabriel Kerneis
2014-02-22 20:24 ` Richard W.M. Jones
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140222143035.GB19246@notk.org \
--to=adrien@notk.org \
--cc=benoit.vaugon@gmail.com \
--cc=caml-list@inria.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).