From: Erick Tryzelaar <erickt@dslextreme.com>
To: Jon Harrop <jon@ffconsultancy.com>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Concurrent ocamlbuild
Date: Sun, 04 Nov 2007 10:06:05 -0800 [thread overview]
Message-ID: <472E0A0D.3010106@dslextreme.com> (raw)
In-Reply-To: <200711041309.44590.jon@ffconsultancy.com>
Did you see the -j N option?
> ocamlbuild -h
...
-j <N> Allow N jobs at once (0 for unlimited)
...
Jon Harrop wrote:
> When I'm not cuddling my dual core, I enjoy using tools such as POVRay,
> pbzip2, quake4-smp and ocamlbuild.
>
> Unfortunately, ocamlbuild only seems to spawn a single compile at a time,
> leaving my other core twiddling its thumbs.
>
> Call me crazy, but I was thinking of forking ocamlbuild and doing a complete
> rewrite in a high-level language like JoCaml. However, I fear my boss will
> object on the grounds that finding me a successor versed in fringe languages
> like JoCaml would be prohibitively difficult. I'll ask her when she's
> finished making lunch but, in the mean time, what do you guys think?
next prev parent reply other threads:[~2007-11-04 18:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-04 13:09 Jon Harrop
2007-11-04 18:06 ` Erick Tryzelaar [this message]
2007-11-05 10:11 ` [Caml-list] " Jon Harrop
2007-11-05 10:49 ` Nicolas Pouillard
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=472E0A0D.3010106@dslextreme.com \
--to=erickt@dslextreme.com \
--cc=caml-list@inria.fr \
--cc=jon@ffconsultancy.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