caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: "Nathaniel Gray" <n8gray@gmail.com>
To: "Nathan Mishra Linger" <nathan.mishralinger@gmail.com>
Cc: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] can ocamldep order .cmo files?
Date: Mon, 14 Aug 2006 23:45:23 -0700	[thread overview]
Message-ID: <aee06c9e0608142345y36e86585n48bb928e24694cc9@mail.gmail.com> (raw)
In-Reply-To: <ab0c618e0608111515yee50b18v527c8920ea540849@mail.gmail.com>

On 8/11/06, Nathan Mishra Linger <nathan.mishralinger@gmail.com> wrote:
> I'm a new OCaml user and quite a fan so far (most of my functional
> programming experience has been in Haskell up to this point).
>
> I know that .cmo arguments to ocamlc must be in order of dependency.
> I also know that ocamldep can detect such dependencies and spit them
> out in a format that makefiles can include.
>
> But can ocamldep spit out the dependency ordering of a list of .cmo
> files in such a way that these can be input to ocamlc?  If not, it
> seems like it would be a useful thing for ocamldep to be able to do
> this.  Or do people have other solutions to this problem.

You might look at the OMake build system[1].  It's a concise and
declarative like make, but with far superior dependency tracking and
support for large projects.  Support for OCaml is particularly strong,
since it's the primary language used for OMake itself and most of the
other projects in our lab.  In particular, it takes care of keeping
the .cmo files in proper order.

Cheers,
-n8

[1] <http://omake.metaprl.org/>
-- 
>>>-- Nathaniel Gray -- Caltech Computer Science ------>
>>>-- Mojave Project -- http://mojave.cs.caltech.edu -->


      parent reply	other threads:[~2006-08-15  6:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-11 22:15 Nathan Mishra Linger
2006-08-11 23:09 ` Till Varoquaux
2006-08-15  6:45 ` Nathaniel Gray [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=aee06c9e0608142345y36e86585n48bb928e24694cc9@mail.gmail.com \
    --to=n8gray@gmail.com \
    --cc=caml-list@yquem.inria.fr \
    --cc=nathan.mishralinger@gmail.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).