From: David Allsopp <dra-news@metastack.com>
To: "Frédéric Bour" <frederic.bour@lakaban.net>,
"caml-list@inria.fr" <caml-list@inria.fr>
Subject: RE: [Caml-list] why is building ocaml hard?
Date: Wed, 13 Jul 2016 12:10:24 +0000 [thread overview]
Message-ID: <E51C5B015DBD1348A1D85763337FB6D9011EA0439F@Remus.metastack.local> (raw)
In-Reply-To: <c4ccb268-95a3-9974-3a64-879a149d8eb6@lakaban.net>
Frédéric Bour wrote:
> More generally, I identify the following problems when building OCaml code:
> - under-specified dependencies, as discussed
> - the compiler driver can produce multiple files on a single invocation.
> File level dependencies turn into an hypergraph rather than a graph (making
> a Makefile driven system hardly stable)
The most horrible one I've found is the production of both .cmi and .cm[ox] for a .ml file with no .mli - it makes parallel compilation of bytecode and native code extremely difficult (for opam - using OCamlMakefile - I found the only way in make was to resort to using lockfile for .ml files with no .mli; of course, I prefer to have a rule that there must always be an .mli, even if it's just `touch foo.mli` to start with!).
Are there other instances where the emitting of multiple files is a stumbling block?
David
next prev parent reply other threads:[~2016-07-13 12:10 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
2016-07-11 7:22 ` Frédéric Bour
2016-07-11 10:36 ` Gerd Stolpmann
2016-07-13 12:10 ` David Allsopp [this message]
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=E51C5B015DBD1348A1D85763337FB6D9011EA0439F@Remus.metastack.local \
--to=dra-news@metastack.com \
--cc=caml-list@inria.fr \
--cc=frederic.bour@lakaban.net \
/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).