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 2BBC77EE49 for ; Thu, 19 Sep 2013 06:35:12 +0200 (CEST) Received-SPF: None (mail3-smtp-sop.national.inria.fr: no sender authenticity information available from domain of krismicinski@gmail.com) identity=pra; client-ip=209.85.214.178; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="krismicinski@gmail.com"; x-sender="krismicinski@gmail.com"; x-conformance=sidf_compatible Received-SPF: Pass (mail3-smtp-sop.national.inria.fr: domain of krismicinski@gmail.com designates 209.85.214.178 as permitted sender) identity=mailfrom; client-ip=209.85.214.178; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="krismicinski@gmail.com"; x-sender="krismicinski@gmail.com"; 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-ob0-f178.google.com) identity=helo; client-ip=209.85.214.178; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="krismicinski@gmail.com"; x-sender="postmaster@mail-ob0-f178.google.com"; x-conformance=sidf_compatible X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AncCAA9+OlLRVdaym2dsb2JhbABbgz9SrwqJXYhGgRsIFg4BAQEBAQYLCwkUKIIlAQEEAUABGx0BAwELBgUEBwM4IQEBEQEFARwGEwiHaAEDCQacJ4xRgweEDwoZJw1kiHgBBQyMb4JsB4QeA5YSgWmBL4sSA4NHGCmEaCA X-IPAS-Result: AncCAA9+OlLRVdaym2dsb2JhbABbgz9SrwqJXYhGgRsIFg4BAQEBAQYLCwkUKIIlAQEEAUABGx0BAwELBgUEBwM4IQEBEQEFARwGEwiHaAEDCQacJ4xRgweEDwoZJw1kiHgBBQyMb4JsB4QeA5YSgWmBL4sSA4NHGCmEaCA X-IronPort-AV: E=Sophos;i="4.90,934,1371074400"; d="scan'208";a="27338358" Received: from mail-ob0-f178.google.com ([209.85.214.178]) by mail3-smtp-sop.national.inria.fr with ESMTP/TLS/RC4-SHA; 19 Sep 2013 06:35:11 +0200 Received: by mail-ob0-f178.google.com with SMTP id uy5so9282196obc.9 for ; Wed, 18 Sep 2013 21:35:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=Jy2VhGmDBGuOMnOVEGtge8jeFkOpLoObNFfHKLEuCRs=; b=KPCtT5z2JReRxDcf1JdFfKxQAhXwYaPcN5cxA1AKBiJwj2/pG3wmwEl9poutZQDkNc 9cN3Y95k+/IuH7psZqAQE3xm/OPkgOypLRycJ7fK+9F+QDcf23ZkFhqtyAiWVcnuaSRR P9IE6J0B+qyY5DsfYU6AKlGg6VB9k4UVkNGLb2veOAXE/D6mi6LGwUFXDmOHSldBvT0b BAZ/+NddlPGa2dwIEgtZDEE0w3e1xCHEbsFeshOkrB7A2dfC3j/zG2tU7qtvjG+i3OM2 HELi81j47pbHzAwNWJPRv/VI83MNaV6lEPf1Zrynccdcj9uLZgVdpg3C0UnaoPYIdsPH FmwQ== MIME-Version: 1.0 X-Received: by 10.182.71.82 with SMTP id s18mr37469550obu.9.1379565309666; Wed, 18 Sep 2013 21:35:09 -0700 (PDT) Received: by 10.182.96.34 with HTTP; Wed, 18 Sep 2013 21:35:09 -0700 (PDT) In-Reply-To: <87bo3pqy9o.fsf@golf.niidar.ru> References: <036501ceb3e5$bcd7b920$36872b60$@ffconsultancy.com> <87bo3pqy9o.fsf@golf.niidar.ru> Date: Thu, 19 Sep 2013 00:35:09 -0400 Message-ID: From: Kristopher Micinski To: Ivan Gotovchits Cc: jon@ffconsultancy.com, Caml List Content-Type: multipart/alternative; boundary=e89a8fb1fde63a74e704e6b5141d Subject: Re: [Caml-list] OCaml on Android --e89a8fb1fde63a74e704e6b5141d Content-Type: text/plain; charset=ISO-8859-1 With a little bit of hacking it'd probably work, but I'm not sure of the status of ocaml-java and haven't looked into the implementation details. Since ocaml-java outputs class files (afaik) you'd have to sort of hack the android build pipeline yourself, but that wouldn't be the hard part: all the tools are there. The harder part is that the Android SDK is very Java oriented, and it just feels awkward as hell to use in OCaml even if you were to write a thin wrapper around the SDK. Kris On Wed, Sep 18, 2013 at 11:35 PM, Ivan Gotovchits wrote: > Kristopher Micinski writes: > > > The basic problem with running OCaml on Android is that pretty much > > everything (minus a few system services / daemons, for example) runs > > inside a Dalvik VM. Everything that is a "real app" thus uses the > > facilities of the SDK to interact with the underlying > > system. (Various services such as internet can be opened via a raw > > socket, and are protected via lower level system modifications.) > > And what about OCaml-Java [1]. Will it be possible to use it with > dalvik? > > [1] http://ocamljava.x9c.fr/preview/ > > -- > (__) > (oo) > /------\/ > / | || > * /\---/\ > ~~ ~~ > ...."Have you mooed today?"... > --e89a8fb1fde63a74e704e6b5141d Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
With a little bit of hacking it'd probably work, but I= 'm not sure of the status of ocaml-java and haven't looked into the= implementation details. =A0Since ocaml-java outputs class files (afaik) yo= u'd have to sort of hack the android build pipeline yourself, but that = wouldn't be the hard part: all the tools are there. =A0The harder part = is that the Android SDK is very Java oriented, and it just feels awkward as= hell to use in OCaml even if you were to write a thin wrapper around the S= DK.

Kris


On Wed, Sep 18, 2013 at 11:35 PM, Ivan Got= ovchits <ivg@ieee.org> wrote:
Kristopher Micinski <krismicinski@gmail.com> writ= es:

> The basic problem with running OCaml on Android is that pretty much
> everything (minus a few system services / daemons, for example) runs > inside a Dalvik VM. =A0Everything that is a "real app" thus = uses the
> facilities of the SDK to interact with the underlying
> system. =A0(Various services such as internet can be opened via a raw<= br> > socket, and are protected via lower level system modifications.)

And what about OCaml-Java [1]. Will it be possible to use it with
dalvik?

[1] http://o= camljava.x9c.fr/preview/

--
=A0 =A0 =A0 =A0 =A0(__)
=A0 =A0 =A0 =A0 =A0(oo)
=A0 =A0/------\/
=A0 / | =A0 =A0||
=A0* =A0/\---/\
=A0 =A0 ~~ =A0 ~~
...."Have you mooed today?"...

--e89a8fb1fde63a74e704e6b5141d--