From: "Jonathan Roewen" <jonathan.roewen@gmail.com>
To: micha <micha-1@fantasymail.de>
Cc: "caml users" <caml-list@inria.fr>
Subject: Re: [Caml-list] wince question
Date: Thu, 28 Sep 2006 07:48:13 +1200 [thread overview]
Message-ID: <ad8cfe7e0609271248k314640ccwda99b3a3fff04a92@mail.gmail.com> (raw)
In-Reply-To: <20060927192136.15b8f70f@localhost>
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
>
next prev parent reply other threads:[~2006-09-27 19:48 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 ` Jonathan Roewen [this message]
2006-09-28 7:29 ` [Caml-list] " Neil Bartlett
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=ad8cfe7e0609271248k314640ccwda99b3a3fff04a92@mail.gmail.com \
--to=jonathan.roewen@gmail.com \
--cc=caml-list@inria.fr \
--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