From: Jonathan Bryant <jtbryant@valdosta.edu>
To: caml-list@inria.fr
Subject: Re: [Caml-list] Caml on intel-OSX
Date: Thu, 09 Jun 2005 19:44:08 -0400 [thread overview]
Message-ID: <1118360648.17936.15.camel@chunky.valdosta.edu> (raw)
In-Reply-To: <36973.131.254.50.45.1118334009.squirrel@mail.irisa.fr>
ocamlc with the "-custon" flag makes standalone bytecode programs (it
embeds a copy of the ZAM, which it generates a slighly larger
executable). But, like was was said earlier, any external libraries
referenced (Dbm, etc.) would have to be included. I think they can be
linked in using a flag, but I don't know. I do know that any external
non-caml libraries (.a & .so files) are not linked in. I almost
exclusively use the native code compiler and may be mistaken, so check
the documentation. Check out the O'Really [sic] OCaml book ("Developing
Applications with OCaml") on the OCaml website: it has a pretty decently
good discussion of this.
--Jonathan
On Thu, 2005-06-09 at 12:20, padiolea@irisa.fr wrote:
> > On Thu, 2005-06-09 at 07:00 -0700, james woodyatt wrote:
> >> On 08 Jun 2005, at 22:33, John Skaller wrote:
> >> >
> >> > And a dumb question .. will a bytecode Ocaml program
> >> > just run on any machine provided a single binary,
> >> > ocamlrun, is installed and accessible?
> >>
> >> You probably want all the ocaml tools to be built as universal binaries
> >> and you probably also want the ocamlopt compiler to be able to produce
> >> universal binaries. I would expect that will require some effort from
> >> the Caml Team at INRIA.
> >
> > Lol! no, it is a simple question. Can I make a bytecode program
> > and just ship it an expect it to run? No. So what else is required?
>
> I guess that if your bytecode program require some external libraries,
> such as for instance if you do a "open Dbm" then you must
> have too this library.
> I think that ocamlrun only include code to handle the Pervasive
> library.
>
>
>
> _______________________________________________
> 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
prev parent reply other threads:[~2005-06-09 23:44 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-09 5:33 John Skaller
2005-06-09 8:23 ` [Caml-list] " Agustín Valverde
2005-06-09 14:00 ` james woodyatt
2005-06-09 15:27 ` John Skaller
2005-06-09 16:20 ` padiolea
2005-06-09 22:51 ` John Skaller
2005-06-10 0:02 ` Jonathan Bryant
2005-06-10 2:55 ` John Skaller
2005-06-10 7:10 ` Florian Hars
2005-06-10 0:41 ` Jacques Garrigue
2005-06-10 1:57 ` John Skaller
2005-06-14 0:28 ` Sven Luther
2005-06-10 6:35 ` Stefano Zacchiroli
2005-06-10 9:07 ` John Skaller
2005-06-10 23:39 ` Jon Harrop
2005-06-11 18:39 ` John Skaller
2005-06-11 19:03 ` Jon Harrop
2005-06-12 6:58 ` John Skaller
2005-06-13 19:19 ` [Caml-list] AMD64 ocamlopt bug Xavier Leroy
2005-06-13 19:32 ` John Skaller
2005-06-13 20:18 ` Damien Doligez
2005-06-13 20:27 ` John Skaller
2005-06-13 21:01 ` Anil Madhavapeddy
2005-06-09 23:44 ` Jonathan Bryant [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=1118360648.17936.15.camel@chunky.valdosta.edu \
--to=jtbryant@valdosta.edu \
--cc=caml-list@inria.fr \
/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).