From: Xavier Leroy <xavier.leroy@inria.fr>
To: Wheeler Ruml <ruml@parc.com>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] VxWorks? mailing list?
Date: Sun, 30 Mar 2003 12:26:43 +0200 [thread overview]
Message-ID: <20030330122643.D22539@pauillac.inria.fr> (raw)
In-Reply-To: <16003.43377.636464.160830@katsura.parc.xerox.com>; from ruml@parc.com on Thu, Mar 27, 2003 at 05:46:25PM -0800
> Has anyone heard of running OCaml programs under the VxWorks real-time
> OS from WindRiver? People who build actual products are asking me if
> my OCaml code can run under VxWorks and I'd appreciate hearing about
> any experiences others have had with either compiling the byte-code
> interpreter or getting native code to work for any of the VxWorks
> targets. Wouldn't it be nice if we could point to OCaml code in
> everyday office products?
I have no experience with VxWorks, but from their Web site it appears
to be POSIX-compliant. If so, chances are very high that the bytecode
interpreter will compile and work right out of the box. For the
native-code compiler, the porting effort can range from the trivial
(e.g. one of the supported configurations just happens to work) to the
fairly hard (e.g. a new code generator has to be written). It's not
possible to say without more details on the target platform and
environment.
- Xavier Leroy
-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
next prev parent reply other threads:[~2003-03-30 10:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-28 1:46 Wheeler Ruml
2003-03-30 10:26 ` Xavier Leroy [this message]
2003-03-30 18:13 ` David Brown
2003-03-30 20:27 ` james woodyatt
2003-04-02 18:15 ` [Caml-list] " Wheeler Ruml
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=20030330122643.D22539@pauillac.inria.fr \
--to=xavier.leroy@inria.fr \
--cc=caml-list@inria.fr \
--cc=ruml@parc.com \
/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).