From: David Allsopp <dra-news@metastack.com>
To: caml-list <caml-list@inria.fr>
Subject: RE: [Caml-list] which ocaml build system
Date: Fri, 26 Jul 2013 07:07:07 +0000 [thread overview]
Message-ID: <E51C5B015DBD1348A1D85763337FB6D9CCA87D28@Remus.metastack.local> (raw)
In-Reply-To: <20130726064910.GA13198@dell.happyleptic.org>
rixed@happyleptic.org wrote:
> -[ Fri, Jul 26, 2013 at 07:46:58AM +0200, Adrien Nader ]----
> > > make -j<number > should work.
Only if the Makefile has been written with parallel execution in mind - it's very easy to produce rules which have hidden dependencies encoded in the order of the prerequisites (and which can be darned hard to debug...). Personally, I'd never assume that a Makefile will automatically work with -j (though I do agree that build systems should be written for parallel execution from day 0).
> > You depend on ocamldep however and it has some issues (it's a fairly
> > simple tool that can get things wrong).
>
> Many makefiles have a distinct target for dependencies, which helps here
> (iff the deps do not change very often). Phasing out ocamldep also helps
> wrt recompilation speed.
What do you mean by phasing out ocamldep? An alternate tool, handwritten dependencies (ouch) or something more complex?
David
next prev parent reply other threads:[~2013-07-26 7:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <51ECF4EB.1060301@libertysurf.fr>
2013-07-22 9:07 ` r.3
2013-07-22 15:11 ` Ashish Agarwal
2013-07-23 13:39 ` Marek Kubica
2013-07-25 21:45 ` Martin DeMello
2013-07-26 1:10 ` Francois Berenger
2013-07-26 5:01 ` Malcolm Matalka
2013-07-26 5:46 ` Adrien Nader
2013-07-26 6:49 ` rixed
2013-07-26 7:07 ` David Allsopp [this message]
2013-07-26 4:49 ` Gabriel Scherer
2013-08-05 17:34 ` [Caml-list] character syntax error '^M' r.3
2013-08-05 17:38 ` David Allsopp
2013-08-05 20:23 ` William R
2013-08-06 10:52 ` David Allsopp
2013-07-27 9:51 ` [Caml-list] which ocaml build system Goswin von Brederlow
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=E51C5B015DBD1348A1D85763337FB6D9CCA87D28@Remus.metastack.local \
--to=dra-news@metastack.com \
--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).