From: Gerd Stolpmann <gerd@gerd-stolpmann.de>
To: Berke Durak <berke.durak@gmail.com>
Cc: "Markus Weißmann" <markus.weissmann@in.tum.de>,
caml-list <caml-list@inria.fr>
Subject: Re: [Caml-list] OCaml embedded
Date: Fri, 26 Jun 2015 23:25:16 +0200 [thread overview]
Message-ID: <1435353916.16506.0.camel@e130.lan.sumadev.de> (raw)
In-Reply-To: <CAALTfKCXSw3+KXmSca+8eTt1_TBrqAE-cd_U4Yor-nvoGdr1EQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1633 bytes --]
Am Donnerstag, den 25.06.2015, 23:04 -0400 schrieb Berke Durak:
> To conclude, as powerful ARM systems are very cheap and plentiful
> these days, and since the convenience of Opam is immense, I'm not sure
> there is much incentive in using a cross-compiler.
There is when you develop for a closed system like iOS.
Also, there is now arm64, and so far I know there are no boards yet.
> BTW, is there a maintained ARM cross-compiler?
It's in mainline, 4.02.2. It's still a little bit difficult to use,
because IMHO some convenience targets are missing in the Makefile.
Whitequark in his Android packages just generates a configuration and
avoids the problems (see
https://github.com/whitequark/opam-android/blob/master/packages/ocaml-android32.4.02.2/files/config/Makefile.in, it is in particular essential to set CAMLRUN to the host compiler's ocamlrun). For the iOS branch (not yet in mainline) we added cross-all and cross-opt targets to the Makefile (see https://github.com/gerdstolpmann/ocaml/tree/gs-4.02.2+ios). This might be easier to start with (this branch contains the changes required for the iOS assembler, but should also work for a GNU toolchain). See the build.sh script in this repo for an example how to configure and build.
Gerd
--
------------------------------------------------------------
Gerd Stolpmann, Darmstadt, Germany gerd@gerd-stolpmann.de
My OCaml site: http://www.camlcity.org
Contact details: http://www.camlcity.org/contact.html
Company homepage: http://www.gerd-stolpmann.de
------------------------------------------------------------
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
prev parent reply other threads:[~2015-06-26 21:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-23 10:07 xavier deschuyteneer
2015-06-23 10:32 ` Markus Weißmann
2015-06-26 3:04 ` Berke Durak
2015-06-26 5:40 ` Kenneth Adam Miller
2015-06-26 5:40 ` Kenneth Adam Miller
2015-06-26 8:18 ` Francois Berenger
2015-06-26 9:57 ` xavier deschuyteneer
2015-06-26 13:39 ` Pierre-Alexandre Voye
2015-07-16 10:06 ` Goswin von Brederlow
2015-07-16 18:45 ` xavier deschuyteneer
2015-06-26 21:25 ` Gerd Stolpmann [this message]
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=1435353916.16506.0.camel@e130.lan.sumadev.de \
--to=gerd@gerd-stolpmann.de \
--cc=berke.durak@gmail.com \
--cc=caml-list@inria.fr \
--cc=markus.weissmann@in.tum.de \
/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