Re: [Caml-list] whither portability?

[Gerd Stolpmann <info@gerd-stolpmann.de>]

[-- Attachment #1: Type: text/plain, Size: 1225 bytes --]

Am Samstag, den 26.09.2015, 18:59 +0300 schrieb whitequark:
> With opam-android, the workflow is exactly identical to building any
> regular OCaml project, with the difference that the final binary 
> produced
> is a .o or .so file that you can use as any other C library in
> your Android project; the Android cross-toolchain is just another switch
> in opam.
> 
> I don't know how it works for iOS but it is almost certainly possible
> to achieve the same level of convenience.

On iOS you just use ocamlopt -output-obj to get a .o and link this into
your app together with libasmrun.a (apps cannot use shared libraries on
iOS so creating an .so is pointless). You can also create a standalone
executable, but this is only useful for jailbroken devices. 

Note that even bytecode works on the device. Maybe useful for a toploop
on the go?

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 --]