caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Yaron Minsky <yminsky@janestreet.com>
To: Alain Frisch <alain@frisch.fr>
Cc: Mark Shinwell <mshinwell@janestreet.com>,
	Gerd Stolpmann <info@gerd-stolpmann.de>,
	 Bob Zhang <bobzhang1988@gmail.com>,
	Caml List <caml-list@inria.fr>
Subject: Re: [Caml-list] improve omake [was One build system to rule them all]
Date: Tue, 23 Sep 2014 22:35:01 -0400	[thread overview]
Message-ID: <CACLX4jSPYNBN77QTr5GiWpjF1DQBBrbGyYLs0S4j-UEAdvuqoQ@mail.gmail.com> (raw)
In-Reply-To: <5421D42A.2070504@frisch.fr>

No joke.  The switch required a fair bit of cleverness on our part.
We actually had some clever intermediate stage when we were building
jenga build description files (full of s-expressions, not OCaml code)
from omake build rules, as a way of bridging the gap as we did the
conversion.  Flipping a big codebase is not for the faint of heart.

y

On Tue, Sep 23, 2014 at 4:12 PM, Alain Frisch <alain@frisch.fr> wrote:
> On 9/23/2014 12:58 PM, Mark Shinwell wrote:
>>
>> I think the details are hazy now, but as far as we recall: your
>> statement about avoiding recomputation is correct, but a lot of md5sum
>> work happened subsequent to each compilation action in serial, within
>> the omake process.
>
>
> Ok, this could affect total compilation built time, not startup (and total
> time when nothing needs to be rebuilt).
>
>> By no means was this the only problem; another, for example, was a
>> vast amount of time spent constructing rules for an entire tree even
>> if only a small portion was being demanded to be built.
>
>
> Ok.  Do you remember if you had some clue about the source of inefficiency
> (evaluator, data structure to represent the environment, etc)?
>
>> (Of course, the worst problem with omake was probably the DSL, which
>> we found to be wholly unsuitable for large-scale reliable rule
>> engineering.  Programmability really is key.)
>
>
> YMMV.  LexiFi's experience with the omake DSL is that even if sometime
> annoying, it's possible to achieve a reasonable effect with some efforts.
> At least, the issues with the DSL did not compensate the other nice
> properties of omake.  I assume that other groups have functional build
> systems implemented with omake as well, so if people working on omake can
> improve its performances, it would be an immediate gain. That's not to say
> that we don't keep an eye open on alternative build systems such as Jenga
> (but switching an entire project to a different build system is a daunting
> task, of course).
>
>
> Alain

  reply	other threads:[~2014-09-24  2:35 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-18 20:14 Bob Zhang
2014-09-18 20:30 ` Aleksey Nogin
2014-09-20 14:59   ` Jun Furuse
2014-09-18 20:34 ` Sébastien Dailly
2014-09-18 21:32 ` Yaron Minsky
2014-09-19 12:23 ` Alain Frisch
2014-09-19 12:29   ` Nicolas Boulay
2014-09-19 13:36   ` Gerd Stolpmann
2014-09-19 14:00     ` Alain Frisch
2014-09-19 15:18       ` Yaron Minsky
2014-09-19 17:18         ` Gerd Stolpmann
2014-09-19 17:48           ` Yaron Minsky
2014-09-23 10:40         ` Alain Frisch
2014-09-23 10:58           ` Mark Shinwell
2014-09-23 20:12             ` Alain Frisch
2014-09-24  2:35               ` Yaron Minsky [this message]
2014-09-22 15:33 Bob Zhang
2014-09-24 13:37 ` Gerd Stolpmann
2014-09-24 15:47   ` Alain Frisch

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=CACLX4jSPYNBN77QTr5GiWpjF1DQBBrbGyYLs0S4j-UEAdvuqoQ@mail.gmail.com \
    --to=yminsky@janestreet.com \
    --cc=alain@frisch.fr \
    --cc=bobzhang1988@gmail.com \
    --cc=caml-list@inria.fr \
    --cc=info@gerd-stolpmann.de \
    --cc=mshinwell@janestreet.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).