From: Martin DeMello <martindemello@gmail.com>
To: Gerd Stolpmann <info@gerd-stolpmann.de>
Cc: "caml-list@inria.fr" <caml-list@inria.fr>
Subject: Re: [Caml-list] why is building ocaml hard?
Date: Sun, 10 Jul 2016 23:15:37 -0700 [thread overview]
Message-ID: <CAFrFfuGLRLam3AWac9OnWF5VQfzFBzjqhtswNwNscXuUz57N+w@mail.gmail.com> (raw)
In-Reply-To: <1468148606.25014.58.camel@e130.lan.sumadev.de>
[-- Attachment #1: Type: text/plain, Size: 1134 bytes --]
On Sun, Jul 10, 2016 at 4:03 AM, Gerd Stolpmann <info@gerd-stolpmann.de>
wrote:
> So how to fix this? In my opinion there are two solutions. You can
> either have a more intelligent ocamldep (e.g. one that reads in
> non-local cmi files and uses that information and also tries to
> interpret all project ml files at once and not file by file - btw, did
> anybody check whether there is an algorithm that precisely solves the
> problem?). The other solution path is to mark toplevel modules in the
> syntax of OCaml (e.g. you'd have to do "open ^M2" is M2 is a toplevel
> module).
>
Would an acceptable third option be to simply record the dag explicitly in
your build file? Working with google's build system [opensourced as bazel:
http://www.bazel.io/] has given me a great appreciation for simply writing
out build dependencies manually; sure, it is relatively tedious to have to
write out the graph yourself rather than have ocamldep figure it out, but
the time and effort to do so is a small fraction of the overall development
time of your project, and the reward is a 100% reliable "detection" of the
build topology.
martin
[-- Attachment #2: Type: text/html, Size: 1620 bytes --]
next prev parent reply other threads:[~2016-07-11 6:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-10 4:16 Martin DeMello
2016-07-10 11:03 ` Gerd Stolpmann
2016-07-10 11:33 ` [Caml-list] Is there an efficient precise ocamldep - Was: " Gerd Stolpmann
2016-07-10 11:51 ` Petter A. Urkedal
2016-07-10 22:41 ` [Caml-list] " Tom Ridge
2016-07-11 6:15 ` Martin DeMello [this message]
2016-07-11 7:22 ` Frédéric Bour
2016-07-11 10:36 ` Gerd Stolpmann
2016-07-13 12:10 ` David Allsopp
2016-07-11 9:14 ` Malcolm Matalka
2016-07-12 8:18 ` 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=CAFrFfuGLRLam3AWac9OnWF5VQfzFBzjqhtswNwNscXuUz57N+w@mail.gmail.com \
--to=martindemello@gmail.com \
--cc=caml-list@inria.fr \
--cc=info@gerd-stolpmann.de \
/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