From: "Daniel Bünzli" <daniel.buenzli@erratique.ch>
To: OCaml List <caml-list@yquem.inria.fr>
Subject: Re: [Caml-list] ocamlbuild & deps
Date: Fri, 20 Feb 2009 17:31:43 +0100 [thread overview]
Message-ID: <E7CB7566-4DA9-40D1-A205-C9E4E478F6D1@erratique.ch> (raw)
In-Reply-To: <499ECEB7.6010709@lri.fr>
Le 20 févr. 09 à 16:39, Romain Bardou a écrit :
> I think there is a difference. It is indeed an optimization issue
> but not at the level of Ocamlbuild itself : it is as the level of
> your compilation process. If A *dynamically* depends on B, and your
> whole project (say, 10 hours of compilation) depends on A, but you
> have no way to build B, then Ocamlbuild will start to compile your
> project until it finds out that A cannot be built (maybe several
> hours later). If B had been put as a ~dep, then Ocamlbuild would not
> even had started building the project in the first place, saving you
> a lot of time.
Heu no. If B cannot be built then the compilation of A stops and the
compilation of your project stops.
It is however true that if A has a dependency on a heavy C in parallel
to B you'll have to wait for the end of C. But even in this case, it's
just a matter of calling 'build' with B and C in a sensible order (and
not in parallel).
Best,
Daniel
next prev parent reply other threads:[~2009-02-20 16:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-20 14:01 Daniel Bünzli
2009-02-20 15:39 ` [Caml-list] " Romain Bardou
2009-02-20 16:31 ` Daniel Bünzli [this message]
2009-02-21 18:53 ` Romain Bardou
2009-02-21 20:19 ` Daniel Bünzli
2009-02-21 20:23 ` Daniel Bünzli
2009-02-26 13:04 ` Daniel Bünzli
2009-03-02 13:43 ` Daniel Bünzli
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=E7CB7566-4DA9-40D1-A205-C9E4E478F6D1@erratique.ch \
--to=daniel.buenzli@erratique.ch \
--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).