From: "Neil Bartlett" <neil@integility.com>
To: "Jonathan Roewen" <jonathan.roewen@gmail.com>
Cc: micha <micha-1@fantasymail.de>, "caml users" <caml-list@inria.fr>
Subject: Re: [Caml-list] wince question
Date: Thu, 28 Sep 2006 08:29:13 +0100 [thread overview]
Message-ID: <bb4674270609280029l911fb37ie737ec78fdcc939c@mail.gmail.com> (raw)
In-Reply-To: <ad8cfe7e0609271248k314640ccwda99b3a3fff04a92@mail.gmail.com>
No problems at all with OCaml (including native code compilation) on
the ARM. I am already running OCaml on a Sharp Zaurus, which is a
Linux-based PDA device with an Intel Xscale processor.
Everything compiled and built straight out of the box - it works like
a dream. Of course WinCE is a whole different kettle of fish.
Regards
Neil
On 9/27/06, Jonathan Roewen <jonathan.roewen@gmail.com> wrote:
> The O'Caml VM is fairly easy to port.
>
> A minimal libc should be enough (excluding Unix module & Threading).
> The rest will require a bit of work, but likely not too much. I have
> the VM running in a freestanding environment (with vmthreads, without
> Unix module), so definitely portable ;-)
>
> As for ocamlopt, I wouldn't know.
>
> Jonathan
>
> On 9/28/06, micha <micha-1@fantasymail.de> wrote:
> >
> > my interest in ocaml on WinCE comes from the fun I would had to
> > demonstrate the power of ocaml to my collegues. We are developing
> > navigation software components in c++ and one primary platform for
> > this are PDAs with WinCE. The chance of switching away from c++ is
> > lesser than zero without being able to run on that platform. Even JAVA
> > runs on those devices allthough a smaller one than normal and a little
> > slow. Ignoring the fact that maybe only few people would like to do a
> > port, what would be the primary tasks to do it? WinCE is quite
> > different from Win32, I don't know how open the ocaml-source is with
> > respect to porting it to another platform (specially ARM CPU).
> >
> > comments and hints are greatly welcome :-)
> >
> > Michael
> >
> > _______________________________________________
> > Caml-list mailing list. Subscription management:
> > http://yquem.inria.fr/cgi-bin/mailman/listinfo/caml-list
> > Archives: http://caml.inria.fr
> > Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
> > Bug reports: http://caml.inria.fr/bin/caml-bugs
> >
>
> _______________________________________________
> Caml-list mailing list. Subscription management:
> http://yquem.inria.fr/cgi-bin/mailman/listinfo/caml-list
> Archives: http://caml.inria.fr
> Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
> Bug reports: http://caml.inria.fr/bin/caml-bugs
>
--
Neil Bartlett
Senior Technical Consultant, Integility Ltd
Tel: +44 (0) 20 7043 8328
Fax: +44 (0) 20 7043 8329
LinkedIn Profile: https://www.linkedin.com/in/neilbartlett
prev parent reply other threads:[~2006-09-28 7:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-27 17:21 micha
2006-09-27 19:48 ` [Caml-list] " Jonathan Roewen
2006-09-28 7:29 ` Neil Bartlett [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=bb4674270609280029l911fb37ie737ec78fdcc939c@mail.gmail.com \
--to=neil@integility.com \
--cc=caml-list@inria.fr \
--cc=jonathan.roewen@gmail.com \
--cc=micha-1@fantasymail.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;
as well as URLs for NNTP newsgroup(s).