From: "Ashish Agarwal" <agarwal1975@gmail.com>
To: "Ben Aurel" <ben.aurel@gmail.com>
Cc: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] Re: how do you compile
Date: Wed, 6 Aug 2008 10:46:03 -0400 [thread overview]
Message-ID: <d8be5ae20808060746p6ca60cd8meea91ed180a17b08@mail.gmail.com> (raw)
In-Reply-To: <74a4f4670808060739h406f7697n8ce63ba4951e871b@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1236 bytes --]
Use ocamlbuild. You can simply type "ocamlbuild lazy_lists.native"
or "ocamlbuild lazy_lists.byte" to produce native or byte code respectively.
All compiled files get put in a separate directory called _build.
On Wed, Aug 6, 2008 at 10:39 AM, Ben Aurel <ben.aurel@gmail.com> wrote:
> > then, the 'files lazy_lists.cmi' and 'lazy_lists.cmo' are not in the
> > /bin directory.
>
> which is bad
>
> On Wed, Aug 6, 2008 at 10:38 AM, Ben Aurel <ben.aurel@gmail.com> wrote:
> > hi
> >
> > If you have a simple source code like
> >
> > lazy_lists.ml
> >
> > what is the best way to compile that in your opinion? I though it
> > would be usefull to have anything but the .ml source code in a bin
> > directory. What do you think of that?
> >
> > If I try that with
> >
> > "ocamlc -o bin/lazy_lists lazy_lists.ml"
> >
> > then, the 'files lazy_lists.cmi' and 'lazy_lists.cmo' are not in the
> > /bin directory.
> >
> > ben
> >
>
> _______________________________________________
> 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
>
[-- Attachment #2: Type: text/html, Size: 2238 bytes --]
prev parent reply other threads:[~2008-08-06 14:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-06 14:38 Ben Aurel
2008-08-06 14:39 ` Ben Aurel
2008-08-06 14:46 ` Ashish Agarwal [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=d8be5ae20808060746p6ca60cd8meea91ed180a17b08@mail.gmail.com \
--to=agarwal1975@gmail.com \
--cc=ben.aurel@gmail.com \
--cc=caml-list@yquem.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).