From: "Ben Aurel" <ben.aurel@gmail.com>
To: caml-list@yquem.inria.fr
Subject: Re: how do you compile
Date: Wed, 6 Aug 2008 10:39:15 -0400 [thread overview]
Message-ID: <74a4f4670808060739h406f7697n8ce63ba4951e871b@mail.gmail.com> (raw)
In-Reply-To: <74a4f4670808060738s41c8b6ddxc61b8e277228542c@mail.gmail.com>
> 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
>
next prev parent reply other threads:[~2008-08-06 14:39 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 [this message]
2008-08-06 14:46 ` [Caml-list] " Ashish Agarwal
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=74a4f4670808060739h406f7697n8ce63ba4951e871b@mail.gmail.com \
--to=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).